[Touch-packages] [Bug 1990891] Re: after today's Kinetic updates, WiFi no longer working, so laptop basically useless
Since this only seems to happen on dist upgrades (or it would after 22.10 is released) and we have a workaround, it doesn't need to be Critical anymore. ** Tags added: regression-upgrade ** Changed in: network-manager (Ubuntu) Importance: Critical => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1990891 Title: after today's Kinetic updates, WiFi no longer working, so laptop basically useless Status in network-manager package in Ubuntu: Confirmed Bug description: ThinkPad X1 Carbon 6th Gen WiFi was working fine. Installed today's batch of Kinetic updates. Laptop can no longer see any WiFi networks (had to dig out my old ThinkPad USB dongle and plug into my router to be able to submit this bug report). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: network-manager 1.40.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 17:09:25 2022 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-08-16 (1137 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IpRoute: default via 192.168.4.1 dev enp0s31f6 proto dhcp src 192.168.4.158 metric 100 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.4.0/24 dev enp0s31f6 proto kernel scope link src 192.168.4.158 metric 100 SourcePackage: network-manager UpgradeStatus: Upgraded to kinetic on 2022-09-24 (2 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.40.0 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1990891/+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 1910768] Re: apport-collect hangs and makes computer hang
[Expired for apport (Ubuntu) because there has been no activity for 60 days.] ** Changed in: apport (Ubuntu) Status: Incomplete => Expired -- 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/1910768 Title: apport-collect hangs and makes computer hang Status in apport package in Ubuntu: Expired Bug description: This bug is related to bug 1723558 (https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1723558) but I could not transfer the generated information. After a crash of bluetoothd (see bug 1910405) I tried to run apport- collect with the bug ID, but the process hangs. After clicking cancel, it makes the computer hang totally, except running teams calls that keep streaming but without interaction possible. All is released when apport is killed manually. The problem also occurs when a crash of the Brave browser causes a call to apport. This bug is generated through ubuntu-bug -w after clicking on the apport-collect window. This second apport process doesn't hang. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport-gtk 2.20.9-0ubuntu7.21 ProcVersionSignature: Ubuntu 5.4.0-58.64~18.04.1-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 8 15:29:04 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2019-11-22 (412 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1910768/+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 1991452] Re: Kinetic boots to black screen
The default VirtualBox settings only give 16MB of graphics memory so the screen will start to fail/turn black around 2K resolution. Please try turning off the virtual machine and changing Video Memory to 64MB. ** Tags added: virtualbox vmwgfx ** 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/1991452 Title: Kinetic boots to black screen Status in Ubuntu: Incomplete Bug description: I installed the kinetic beta this morning in VirtualBox VM (6.1.38-dfsg-3). On the first boot after install, it got as far as the Ubuntu logo and then the screen went black and I couldn't do anything. I tried to reboot it a few times to no avail. Eventually, I rebooted it into recovery mode and used the 'repair broken packages' option and that changed around some packages. The system resumed from recovery mode and brought me to the normal desktop. I used it stably for a while and I rebooted it twice in the normal course of what I was doing with it. It booted to the desktop fine both times. However, when I rebooted it a third time, it booted to the black screen again. I rebooted it into recovery mode and ran the 'repair' again. It didn't change any packages, but resuming from recovery booted me into a usable system. I filed this bug from the terminal directly after that reboot. Expected Result: Consistent boot to desktop Actual Result: Inconsistent boot to a black screen; seemingly fixed by entering and exiting recovery mode lsb_release -rd: Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 apt policy xorg: Installed: 1:7.7+23ubuntu2 Candidate: 1:7.7+23ubuntu2 Version table: *** 1:7.7+23ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 1 13:26:51 2022 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2022-10-01 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox 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-15-generic root=UUID=2628bb97-3fa1-41ab-92ca-3d98c5e16424 ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.112-3ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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/1991452/+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 1990742] Re: screen not consistently locking when lid is closed
Thanks for that. Indeed the log shows the lid being closed without any locking near the end. That might be related to bug 1857392 which is clearly occurring at the same time. It also highlights that systemd is responsible for initiating the locking. ** Package changed: ubuntu => systemd (Ubuntu) ** Changed in: systemd (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1990742 Title: screen not consistently locking when lid is closed Status in systemd package in Ubuntu: New Bug description: I have GNOME configured to lock the screen when the screen is blanked, and to blank the screen when the lid is closed: org.gnome.settings-daemon.plugins.power lid-close-battery-action 'blank' org.gnome.desktop.screensaver lock-delay uint32 0 org.gnome.desktop.screensaver lock-enabled true This worked fine in Jammy: whenever my screen was unlocked and I closed my laptop lid, it locked immediately, i.e., if I immediately reopened my lid, the screen was locked. After having just upgraded to Kinetic, however, sometimes when I close the lid it locks as described above, and sometimes it just... doesn't, i.e., when I open the lid again the screen is unlocked and I can just keep working. I have been unable to determine what the factors are which control whether the screen locks when I close the lid. There is a moderate security implication here, as it's problematic for someone's screen not to lock when they think that it did. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Sep 24 17:57:37 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-16 (1135 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 43.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1990742/+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 1990742] [NEW] screen not consistently locking when lid is closed
*** This bug is a security vulnerability *** You have been subscribed to a public security bug: I have GNOME configured to lock the screen when the screen is blanked, and to blank the screen when the lid is closed: org.gnome.settings-daemon.plugins.power lid-close-battery-action 'blank' org.gnome.desktop.screensaver lock-delay uint32 0 org.gnome.desktop.screensaver lock-enabled true This worked fine in Jammy: whenever my screen was unlocked and I closed my laptop lid, it locked immediately, i.e., if I immediately reopened my lid, the screen was locked. After having just upgraded to Kinetic, however, sometimes when I close the lid it locks as described above, and sometimes it just... doesn't, i.e., when I open the lid again the screen is unlocked and I can just keep working. I have been unable to determine what the factors are which control whether the screen locks when I close the lid. There is a moderate security implication here, as it's problematic for someone's screen not to lock when they think that it did. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Sep 24 17:57:37 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-16 (1135 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 43.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic third-party-packages -- screen not consistently locking when lid is closed https://bugs.launchpad.net/bugs/1990742 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1991494] Re: dark mode sometimes works
** Package changed: xorg (Ubuntu) => gnome-shell (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/1991494 Title: dark mode sometimes works Status in gnome-shell package in Ubuntu: New Bug description: the dark mode sometimes works and sometimes doesn't work. If i open Ubuntu Software store dark mode doesn't work and i have to go back to turn it back on again then it work's, its like it doesn't went to be in dark mode when i open Ubuntu Software store. it doesn't matter that must to me i just want you guys to know about it. this problem in on Ubuntu 22.10 Kinetic Kudu ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-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.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 2 20:18:36 2022 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake GT2 [HD Graphics 520] [1043:135e] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 920MX] [1043:135e] InstallationDate: Installed on 2022-10-02 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1) MachineType: ASUSTeK COMPUTER INC. X541UVK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic root=UUID=70e3626f-9c69-4f70-9d86-7021fd38f8a6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/30/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X541UVK.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X541UVK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX541UVK.308:bd01/30/2018:br5.12:svnASUSTeKCOMPUTERINC.:pnX541UVK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541UVK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: X dmi.product.name: X541UVK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.112-3ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.0-1ubuntu1 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.4-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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/gnome-shell/+bug/1991494/+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 1989989] Re: Microphone not working on Lenovo Yoga 7 Gen 7 AMD (14ARB7)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1989989 Title: Microphone not working on Lenovo Yoga 7 Gen 7 AMD (14ARB7) Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Yoga 7 Gen 7 AMD (14ARB7), the microphone doesn't work. I'm not familiar with the area, but I think that there is no recognized input device at all. When I try to record with any program, no sound is recorded. I think that this problem affects other Lenovo Yoga laptops. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 Uname: Linux 6.0.0-06rc3-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: saverio1949 F pulseaudio /dev/snd/controlC0: saverio1949 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Fri Sep 16 18:15:09 2022 InstallationDate: Installed on 2022-09-15 (1 days ago) InstallationMedia: Ubuntu-MATE 22.04.1-6.0rc3 "Custom Jammy Jellyfish" (20220910) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingPlaybackStderr: o p e n ( ) : N o s u c h f i l e o r d i r e c t o r y Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_AlsaRecordingTestStderr: a r e c o r d : m a i n : 8 3 1 : a u d i o o p e n e r r o r : N o s u c h f i l e o r d i r e c t o r y Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: saverio1949 F pulseaudio /dev/snd/controlC0: saverio1949 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HD-Audio Generic, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2022 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: K5CN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 7 14ARB7 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrK5CN27WW:bd05/08/2022:br1.27:efr1.27:svnLENOVO:pn82QF:pvrYoga714ARB7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct31:cvrYoga714ARB7:skuLENOVO_MT_82QF_BU_idea_FM_Yoga714ARB7: dmi.product.family: Yoga 7 14ARB7 dmi.product.name: 82QF dmi.product.sku: LENOVO_MT_82QF_BU_idea_FM_Yoga 7 14ARB7 dmi.product.version: Yoga 7 14ARB7 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2022-09-15T11:39:08.571662 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1989989/+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 1991494] Re: dark mode sometimes works
** Package changed: ubuntu => xorg (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/1991494 Title: dark mode sometimes works Status in xorg package in Ubuntu: New Bug description: the dark mode sometimes works and sometimes doesn't work. If i open Ubuntu Software store dark mode doesn't work and i have to go back to turn it back on again then it work's, its like it doesn't went to be in dark mode when i open Ubuntu Software store. it doesn't matter that must to me i just want you guys to know about it. this problem in on Ubuntu 22.10 Kinetic Kudu ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-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.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 2 20:18:36 2022 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake GT2 [HD Graphics 520] [1043:135e] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 920MX] [1043:135e] InstallationDate: Installed on 2022-10-02 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1) MachineType: ASUSTeK COMPUTER INC. X541UVK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic root=UUID=70e3626f-9c69-4f70-9d86-7021fd38f8a6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/30/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X541UVK.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X541UVK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX541UVK.308:bd01/30/2018:br5.12:svnASUSTeKCOMPUTERINC.:pnX541UVK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541UVK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: X dmi.product.name: X541UVK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.112-3ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.0-1ubuntu1 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.4-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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/xorg/+bug/1991494/+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 1991494] [NEW] dark mode sometimes works
You have been subscribed to a public bug: the dark mode sometimes works and sometimes doesn't work. If i open Ubuntu Software store dark mode doesn't work and i have to go back to turn it back on again then it work's, its like it doesn't went to be in dark mode when i open Ubuntu Software store. it doesn't matter that must to me i just want you guys to know about it. this problem in on Ubuntu 22.10 Kinetic Kudu ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-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.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 2 20:18:36 2022 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake GT2 [HD Graphics 520] [1043:135e] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 920MX] [1043:135e] InstallationDate: Installed on 2022-10-02 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1) MachineType: ASUSTeK COMPUTER INC. X541UVK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic root=UUID=70e3626f-9c69-4f70-9d86-7021fd38f8a6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/30/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X541UVK.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X541UVK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX541UVK.308:bd01/30/2018:br5.12:svnASUSTeKCOMPUTERINC.:pnX541UVK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541UVK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: X dmi.product.name: X541UVK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.112-3ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.0-1ubuntu1 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.4-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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 kinetic ubuntu -- dark mode sometimes works https://bugs.launchpad.net/bugs/1991494 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1991495] [NEW] gnome-gmail does not work as a helper application
Public bug reported: To enable gnome-gmail to work, the sanitized_helper profile in /etc/apparmor.d/abstractions/ubuntu-helpers needs to allow the main script of gnome-gmail to be exec'ed. I have added a minimal change to allow that, which is attached to this bug: # Allow exec of gnome-gmail main script /usr/share/gnome-gmail/gnomegmail.py Pixr, A more general change to support other (potential) helpers might be useful. (Alternatively, this could be considered a gnome-gmail problem—it's a weird way to package a Python program, to use a trivial shell script that execs the main program!) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apparmor 3.0.4-2ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sun Oct 2 20:25:58 2022 InstallationDate: Installed on 2021-02-07 (601 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: UpgradeStatus: Upgraded to jammy on 2022-08-16 (47 days ago) mtime.conffile..etc.apparmor.d.abstractions.ubuntu-helpers: 2022-10-02T20:21:41.874949 ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/1991495 Title: gnome-gmail does not work as a helper application Status in apparmor package in Ubuntu: New Bug description: To enable gnome-gmail to work, the sanitized_helper profile in /etc/apparmor.d/abstractions/ubuntu-helpers needs to allow the main script of gnome-gmail to be exec'ed. I have added a minimal change to allow that, which is attached to this bug: # Allow exec of gnome-gmail main script /usr/share/gnome-gmail/gnomegmail.py Pixr, A more general change to support other (potential) helpers might be useful. (Alternatively, this could be considered a gnome-gmail problem—it's a weird way to package a Python program, to use a trivial shell script that execs the main program!) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apparmor 3.0.4-2ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sun Oct 2 20:25:58 2022 InstallationDate: Installed on 2021-02-07 (601 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: UpgradeStatus: Upgraded to jammy on 2022-08-16 (47 days ago) mtime.conffile..etc.apparmor.d.abstractions.ubuntu-helpers: 2022-10-02T20:21:41.874949 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1991495/+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 1991492] [NEW] Upgrade to version 1.1.0
Public bug reported: Version 1.1.0 (released in March 2022) brings MP3 encoding/decoding support. It would be great if the version here could be updated. ** Affects: libsndfile (Ubuntu) Importance: Undecided Status: New ** Tags: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsndfile in Ubuntu. https://bugs.launchpad.net/bugs/1991492 Title: Upgrade to version 1.1.0 Status in libsndfile package in Ubuntu: New Bug description: Version 1.1.0 (released in March 2022) brings MP3 encoding/decoding support. It would be great if the version here could be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsndfile/+bug/1991492/+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 1991491] [NEW] package initramfs-tools 0.140ubuntu13 failed to install/upgrade: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwe
Public bug reported: I undated from 20.04.5 to 22.04.1 and this is what the update ended with. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: initramfs-tools 0.140ubuntu13 ProcVersionSignature: Ubuntu 5.4.0-126.142-generic 5.4.203 Uname: Linux 5.4.0-126-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Oct 2 19:06:19 2022 ErrorMessage: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück InstallationDate: Installed on 2017-06-03 (1946 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: initramfs-tools Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to jammy on 2022-10-02 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1991491 Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: »installiertes initramfs-tools-Skript des Paketes post- installation«-Unterprozess gab den Fehlerwert 1 zurück Status in initramfs-tools package in Ubuntu: New Bug description: I undated from 20.04.5 to 22.04.1 and this is what the update ended with. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: initramfs-tools 0.140ubuntu13 ProcVersionSignature: Ubuntu 5.4.0-126.142-generic 5.4.203 Uname: Linux 5.4.0-126-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Oct 2 19:06:19 2022 ErrorMessage: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück InstallationDate: Installed on 2017-06-03 (1946 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: initramfs-tools Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to jammy on 2022-10-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1991491/+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 1946538] Re: Update to Maliit 2.x
maliit-framework 2.2.1-2.1ubuntu2 is now available for all architectures in Ubuntu Kinetic (https://bugs.launchpad.net/ubuntu/+source/maliit- framework/2.2.1-2.1ubuntu2) ** Changed in: maliit-framework (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to maliit-framework in Ubuntu. https://bugs.launchpad.net/bugs/1946538 Title: Update to Maliit 2.x Status in maliit-framework package in Ubuntu: Fix Released Status in maliit-framework package in Debian: Fix Released Bug description: https://github.com/maliit/framework/releases Your package is ancient. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+bug/1946538/+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 1833863] Re: Incorrect logic for
** Changed in: garcon Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pyxdg in Ubuntu. https://bugs.launchpad.net/bugs/1833863 Title: Incorrect logic for Status in Garcon: New Status in PyXDG: New Status in garcon package in Ubuntu: Triaged Status in pyxdg package in Ubuntu: New Status in xubuntu-default-settings package in Ubuntu: Fix Released Bug description: XFCE & Xubuntu use in their menu files, which python-xdg currently (all current versions) does not handle correctly: https://gitlab.freedesktop.org/xdg/pyxdg/issues/12 I think the fix is as simple as --- Menu.py.a 2019-06-23 17:44:24.992850139 +0100 +++ Menu.py.b 2019-06-23 17:44:41.052807584 +0100 @@ -997,7 +997,7 @@ for menuentry in menu.MenuEntries: if menuentry not in tmp_e: menu.Entries.append(menuentry) -elif order[1] == "menus" or order[1] == "all": +if order[1] == "menus" or order[1] == "all": menu.Submenus.sort() for submenu in menu.Submenus: if submenu.Name not in tmp_s: But as it can also be trivially worked around by replacing with , I wonder if this should be done in XFCE/Xubuntu? To manage notifications about this bug go to: https://bugs.launchpad.net/garcon/+bug/1833863/+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 1991477] [NEW] package linux-image-5.15.0-48-generic 5.15.0-48.54 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: Trying to upgrade to the latest image. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.4.0-126.142-generic 5.4.203 Uname: Linux 5.4.0-126-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 2 01:45 seq crw-rw 1 root audio 116, 33 Oct 2 01:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown Date: Sun Oct 2 01:51:16 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M MachineType: DigitalOcean Droplet PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-126-generic root=UUID=db153994-91fe-426f-bd88-f751e07f97f2 ro console=tty1 console=ttyS0 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu7 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: initramfs-tools Title: package linux-image-5.15.0-48-generic 5.15.0-48.54 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to jammy on 2022-10-02 (0 days ago) dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check uec-images -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1991477 Title: package linux-image-5.15.0-48-generic 5.15.0-48.54 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: Trying to upgrade to the latest image. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.4.0-126.142-generic 5.4.203 Uname: Linux 5.4.0-126-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 2 01:45 seq crw-rw 1 root audio 116, 33 Oct 2 01:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown Date: Sun Oct 2 01:51:16 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M MachineType: DigitalOcean Droplet PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-126-generic root=UUID=db153994-91fe-426f-bd88-f751e07f97f2 ro console=tty1 console=ttyS0 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu7 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: initramfs-tools Title: package linux-image-5.15.0-48-generic 5.15.0-48.54 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to jammy on 2022-10-02 (0 days ago) dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to:
