[Touch-packages] [Bug 1945883] [NEW] Error failed to install/upgrade initramfs-tools 0.136ubuntu6.6
Public bug reported: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Oct 2 23:16:52 2021 ErrorMessage: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2021-10-03 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1945883 Title: Error failed to install/upgrade initramfs-tools 0.136ubuntu6.6 Status in initramfs-tools package in Ubuntu: New Bug description: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Oct 2 23:16:52 2021 ErrorMessage: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2021-10-03 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1945883/+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 1945880] [NEW] [X570 AORUS ELITE, Realtek ALCS1200A, Green Line Out, Rear] Playback problem
Public bug reported: Ground noise when starting system - only goes away when I play back something or when there are system sounds. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Oct 3 02:17:32 2021 InstallationDate: Installed on 2021-10-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: LANGUAGE=de_CH:de PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_CH.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [X570 AORUS ELITE, Realtek ALCS1200A, Green Line Out, Rear] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F33h dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33h:bd04/23/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:skuDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1945880 Title: [X570 AORUS ELITE, Realtek ALCS1200A, Green Line Out, Rear] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: Ground noise when starting system - only goes away when I play back something or when there are system sounds. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Oct 3 02:17:32 2021 InstallationDate: Installed on 2021-10-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: LANGUAGE=de_CH:de PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_CH.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [X570 AORUS ELITE, Realtek ALCS1200A, Green Line Out, Rear] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F33h dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33h:bd04/23/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:skuDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1945880/+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 1938983] Re: missing modules after 5.11.0-25-generic update
@MikeR: Thanks. I downloaded the missing bin files as you explained in #7 and get rid of the errors. However, my wifi was NOT coming back under kernel 5.11.x (still worked fine when booting 5.8.x) In my case (Broadcom BCM4313 802.11ac), I had to install a different (backported) version of the bcmwl-kernel-source package, see https://askubuntu.com/questions/1356061/bcm4352-802-11ac-wireless-network-adapter-not-working-on-kernel-5-11-and-ubuntu -- 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/1938983 Title: missing modules after 5.11.0-25-generic update Status in initramfs-tools package in Ubuntu: Confirmed Bug description: After updating to kernel 5.11.0-25-generic wireless driver failed to recognize WiFi card. Possible reasons/symptoms: $ sudo update-initramfs -u -k all update-initramfs: Generating /boot/initrd.img-5.11.0-25-generic W: Possible missing firmware /lib/firmware/i915/skl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cml_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/dg1_dmc_ver2_02.bin for module i915 update-initramfs: Generating /boot/initrd.img-5.8.0-63-generic $ lsb_release -a LSB Version: core-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch Distributor ID: Ubuntu Description: July2021 Release: 20.04 Codename: focal Workaround: connected Ethernet. (Inconvenient) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1938983/+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 1945879] pk-debconf-helper crashed with SIGSEGV in g_main_context_dispatch()
StacktraceTop: pk_client_helper_copy_stdout_cb (source=, condition=, child=0x55cec85af050) at ../lib/packagekit-glib2/pk-client-helper.c:210 g_main_dispatch (context=0x55cec85a6f30) at ../../../glib/gmain.c:3337 g_main_context_dispatch (context=0x55cec85a6f30) at ../../../glib/gmain.c:4055 g_main_context_iterate.constprop.0 (context=0x55cec85a6f30, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4131 g_main_loop_run (loop=0x55cec85a2890) at ../../../glib/gmain.c:4329 ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1945879 Title: pk-debconf-helper crashed with SIGSEGV in g_main_context_dispatch() Status in packagekit package in Ubuntu: New Bug description: This happened while trying to install nvidia server packages. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: packagekit 1.2.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sat Oct 2 14:43:29 2021 ExecutablePath: /usr/libexec/pk-debconf-helper InstallationDate: Installed on 2021-06-10 (114 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcCmdline: /usr/libexec/pk-debconf-helper ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= LANGUAGE=en SegvAnalysis: Segfault happened at: 0x7f05566e8b27:mov0x8(%rax),%rcx PC (0x7f05566e8b27) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rcx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: packagekit StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libpackagekit-glib2.so.18 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () Title: pk-debconf-helper crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: Upgraded to impish on 2021-06-14 (110 days ago) UserGroups: adm cdrom dip lxd plugdev sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1945879/+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 1945879] [NEW] pk-debconf-helper crashed with SIGSEGV in g_main_context_dispatch()
Public bug reported: This happened while trying to install nvidia server packages. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: packagekit 1.2.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sat Oct 2 14:43:29 2021 ExecutablePath: /usr/libexec/pk-debconf-helper InstallationDate: Installed on 2021-06-10 (114 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcCmdline: /usr/libexec/pk-debconf-helper ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= LANGUAGE=en SegvAnalysis: Segfault happened at: 0x7f05566e8b27: mov0x8(%rax),%rcx PC (0x7f05566e8b27) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rcx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: packagekit StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libpackagekit-glib2.so.18 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () Title: pk-debconf-helper crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: Upgraded to impish on 2021-06-14 (110 days ago) UserGroups: adm cdrom dip lxd plugdev sudo separator: ** Affects: packagekit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash impish uec-images -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1945879 Title: pk-debconf-helper crashed with SIGSEGV in g_main_context_dispatch() Status in packagekit package in Ubuntu: New Bug description: This happened while trying to install nvidia server packages. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: packagekit 1.2.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sat Oct 2 14:43:29 2021 ExecutablePath: /usr/libexec/pk-debconf-helper InstallationDate: Installed on 2021-06-10 (114 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcCmdline: /usr/libexec/pk-debconf-helper ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= LANGUAGE=en SegvAnalysis: Segfault happened at: 0x7f05566e8b27:mov0x8(%rax),%rcx PC (0x7f05566e8b27) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rcx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: packagekit StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libpackagekit-glib2.so.18 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () Title: pk-debconf-helper crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: Upgraded to impish on 2021-06-14 (110 days ago) UserGroups: adm cdrom dip lxd plugdev sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1945879/+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 1945853] Re: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref()
*** This bug is a duplicate of bug 1943369 *** https://bugs.launchpad.net/bugs/1943369 Norbert, I tested an .iso image with VirtualBox and saw Apport window when I was going to turn off the virtual machine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1945853 Title: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref() Status in glib2.0 package in Ubuntu: Confirmed Status in mate-screensaver package in Ubuntu: Confirmed Bug description: I found this casually when I was testing the latest Ubuntu MATE 21.10 Beta. I have no idea what may cause the crash. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: mate-screensaver 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: MATE Date: Sat Oct 2 07:53:08 2021 ExecutablePath: /usr/bin/mate-screensaver ExecutableTimestamp: 1629565330 LiveMediaBuild: Ubuntu-MATE 21.10 "Impish Indri" - Beta amd64 (20211002) ProcCmdline: mate-screensaver ProcCwd: /home/ubuntu-mate ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fc222155b07 : lock addl $0x1,(%rdi) PC (0x7fc222155b07) ok source "$0x1" ok destination "(%rdi)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: mate-screensaver StacktraceTop: matemenu_tree_item_ref () from /lib/x86_64-linux-gnu/libmate-menu.so.2 gs_theme_manager_lookup_theme_info () ?? () ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1945853/+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 1945859] Re: package linux-image-5.11.0-37-generic 5.11.0-37.41~20.04.2 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127
** Package changed: ubuntu => initramfs-tools (Ubuntu) -- 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/1945859 Title: package linux-image-5.11.0-37-generic 5.11.0-37.41~20.04.2 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 Status in initramfs-tools package in Ubuntu: New Bug description: I don't even know what happeeed, I just got a message telling me something crashed. Happens every day and this is the first time I decided to report it. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-37-generic 5.11.0-37.41~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Sep 30 07:00:55 2021 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 InstallationDate: Installed on 2021-09-22 (10 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package linux-image-5.11.0-37-generic 5.11.0-37.41~20.04.2 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1945859/+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 1945859] [NEW] package linux-image-5.11.0-37-generic 5.11.0-37.41~20.04.2 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127
You have been subscribed to a public bug: I don't even know what happeeed, I just got a message telling me something crashed. Happens every day and this is the first time I decided to report it. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-37-generic 5.11.0-37.41~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Sep 30 07:00:55 2021 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 InstallationDate: Installed on 2021-09-22 (10 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package linux-image-5.11.0-37-generic 5.11.0-37.41~20.04.2 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- package linux-image-5.11.0-37-generic 5.11.0-37.41~20.04.2 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 https://bugs.launchpad.net/bugs/1945859 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools 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 1945853] Re: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref()
*** This bug is a duplicate of bug 1943369 *** https://bugs.launchpad.net/bugs/1943369 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mate-screensaver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1945853 Title: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref() Status in glib2.0 package in Ubuntu: Confirmed Status in mate-screensaver package in Ubuntu: Confirmed Bug description: I found this casually when I was testing the latest Ubuntu MATE 21.10 Beta. I have no idea what may cause the crash. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: mate-screensaver 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: MATE Date: Sat Oct 2 07:53:08 2021 ExecutablePath: /usr/bin/mate-screensaver ExecutableTimestamp: 1629565330 LiveMediaBuild: Ubuntu-MATE 21.10 "Impish Indri" - Beta amd64 (20211002) ProcCmdline: mate-screensaver ProcCwd: /home/ubuntu-mate ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fc222155b07 : lock addl $0x1,(%rdi) PC (0x7fc222155b07) ok source "$0x1" ok destination "(%rdi)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: mate-screensaver StacktraceTop: matemenu_tree_item_ref () from /lib/x86_64-linux-gnu/libmate-menu.so.2 gs_theme_manager_lookup_theme_info () ?? () ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1945853/+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 1945853] Re: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref()
*** This bug is a duplicate of bug 1943369 *** https://bugs.launchpad.net/bugs/1943369 @Nicholas Guriev just curious which hardware do you use? I see the same behavior on old Lenovo SL500 with Core2Duo T9550. ** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1945853 Title: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref() Status in glib2.0 package in Ubuntu: Confirmed Status in mate-screensaver package in Ubuntu: Confirmed Bug description: I found this casually when I was testing the latest Ubuntu MATE 21.10 Beta. I have no idea what may cause the crash. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: mate-screensaver 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: MATE Date: Sat Oct 2 07:53:08 2021 ExecutablePath: /usr/bin/mate-screensaver ExecutableTimestamp: 1629565330 LiveMediaBuild: Ubuntu-MATE 21.10 "Impish Indri" - Beta amd64 (20211002) ProcCmdline: mate-screensaver ProcCwd: /home/ubuntu-mate ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fc222155b07 : lock addl $0x1,(%rdi) PC (0x7fc222155b07) ok source "$0x1" ok destination "(%rdi)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: mate-screensaver StacktraceTop: matemenu_tree_item_ref () from /lib/x86_64-linux-gnu/libmate-menu.so.2 gs_theme_manager_lookup_theme_info () ?? () ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1945853/+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 1945853] Re: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref()
*** This bug is a duplicate of bug 1943369 *** https://bugs.launchpad.net/bugs/1943369 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: glib2.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1945853 Title: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref() Status in glib2.0 package in Ubuntu: Confirmed Status in mate-screensaver package in Ubuntu: Confirmed Bug description: I found this casually when I was testing the latest Ubuntu MATE 21.10 Beta. I have no idea what may cause the crash. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: mate-screensaver 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: MATE Date: Sat Oct 2 07:53:08 2021 ExecutablePath: /usr/bin/mate-screensaver ExecutableTimestamp: 1629565330 LiveMediaBuild: Ubuntu-MATE 21.10 "Impish Indri" - Beta amd64 (20211002) ProcCmdline: mate-screensaver ProcCwd: /home/ubuntu-mate ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fc222155b07 : lock addl $0x1,(%rdi) PC (0x7fc222155b07) ok source "$0x1" ok destination "(%rdi)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: mate-screensaver StacktraceTop: matemenu_tree_item_ref () from /lib/x86_64-linux-gnu/libmate-menu.so.2 gs_theme_manager_lookup_theme_info () ?? () ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: mate-screensaver crashed with SIGSEGV in matemenu_tree_item_ref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1945853/+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 1945867] [NEW] package initramfs-tools 0.136ubuntu6.5 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status
Public bug reported: sdc ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.5 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 NonfreeKernelModules: nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Oct 2 17:05:34 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-05-25 (129 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.5 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- 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/1945867 Title: package initramfs-tools 0.136ubuntu6.5 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: sdc ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.5 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 NonfreeKernelModules: nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Oct 2 17:05:34 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-05-25 (129 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.5 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1945867/+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 1883608] Re: [USB-Audio - UMC204HD 192k, playback] Playback problem
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1883608 Title: [USB-Audio - UMC204HD 192k, playback] Playback problem Status in pulseaudio package in Ubuntu: Confirmed Bug description: I want to split the 4.0 output into 2x2.0 outputs. This is my config for /etc/pulse/default.pa load-module module-remap-sink sink_name=behringera sink_properties="device.description='Behringer Output A (1 and 2)'" remix=no master=alsa_output.usb-BEHRINGER_UMC204HD_192k-00.analog-surround-40 channels=2 master_channel_map=front-left,front-right channel_map=left,right load-module module-remap-sink sink_name=behringerb sink_properties="device.description='Behringer Output B (3 and 4)'" remix=no master=alsa_output.usb-BEHRINGER_UMC204HD_192k-00.analog-surround-40 channels=2 master_channel_map=rear-left,rear-right channel_map=left,right I have tested this config on Ubuntu 18.04, Debian, Fedora 30, it works on all of them. But does not work on Ubuntu 20.04, nor Fedora 32. Both 20.04 and f32 use version 13.99.1 of Pulseaudio, so I suspect the problem to be with this version. When I speak about A and B, I am referring to the device description given in the 2 lines above, line 1 being A and line 2 being B. What is happening on 20.04 and f32 is if I comment out A, then B will work. If I comment out B, A will work, but both A and B are defined, then only A will work. If B is defined first, and then A, something else weird happens where A will work, but is sent out through B, and B will work as expected. A discussion on Reddit, another user has version 13.0 on NixOS and his similar UMC404HD works fine. Here is a link to the info on Reddit: https://www.reddit.com/r/linuxaudio/comments/fqmhbe/pulseaudio_and_multichannel_interfaces/ftkq7ov I know this is probably a pulseaudio bug, but I could not figure out how to submit a bug report to them. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: angus 5429 F pulseaudio /dev/snd/pcmC0D0p: angus 5429 F...m pulseaudio /dev/snd/controlC3: angus 5429 F pulseaudio /dev/snd/controlC2: angus 5429 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 15 23:14:49 2020 InstallationDate: Installed on 2020-04-25 (51 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:U192k successful Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio Generic Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [USB-Audio - UMC204HD 192k, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/21/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.H0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X370 KRAIT GAMING (MS-7A33) 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:bvnAmericanMegatrendsInc.:bvr1.H0:bd01/21/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A33:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX370KRAITGAMING(MS-7A33):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A33 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/pulseaudio/+bug/1883608/+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 1945645] Re: cups-pdf prints blank pages
Thanks. That confirms my suspicions. Debian already has a patch for CUPS-PDF (pending import into Ubuntu) that removes the warning about deprecated Ghostscript options. However, it seems that Ghostscript 9.54 brought in even more unexpected changes that somehow break CUPS-PDF. This will require additional investigation. -- 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/1945645 Title: cups-pdf prints blank pages Status in cups package in Ubuntu: Confirmed Status in cups-pdf package in Ubuntu: Confirmed Status in ghostscript package in Ubuntu: Confirmed Status in ghostscript package in Debian: New Bug description: after updating from ubuntu 21.04 to ubuntu 21.10 the virtual pdf printer started to print blank pages (to create washed pdf files) printer-driver-cups-pdf, version 3.0.1-10 Description:Ubuntu Impish Indri (development branch) Release:21.10 printer-driver-cups-pdf: Installed: 3.0.1-10 Candidate: 3.0.1-10 Version table: *** 3.0.1-10 500 500 http://bg.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: printer-driver-cups-pdf 3.0.1-10 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 30 15:56:51 2021 InstallationDate: Installed on 2020-03-17 (561 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200205) Lpstat: device for PDF: cups-pdf:/ Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied SourcePackage: cups-pdf UpgradeStatus: Upgraded to impish on 2021-09-28 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1945645/+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 1945645] Re: cups-pdf prints blank pages
With the versions from 21.04 everything works fine ghostscript: Installed: 9.53.3~dfsg-7ubuntu0.1 Candidate: 9.54.0~dfsg1-0ubuntu2 Version table: 9.54.0~dfsg1-0ubuntu2 500 500 http://bg.archive.ubuntu.com/ubuntu impish/main amd64 Packages *** 9.53.3~dfsg-7ubuntu0.1 100 100 /var/lib/dpkg/status libgs9: Installed: 9.53.3~dfsg-7ubuntu0.1 Candidate: 9.54.0~dfsg1-0ubuntu2 Version table: 9.54.0~dfsg1-0ubuntu2 500 500 http://bg.archive.ubuntu.com/ubuntu impish/main amd64 Packages *** 9.53.3~dfsg-7ubuntu0.1 100 100 /var/lib/dpkg/status libgs9-common: Installed: 9.53.3~dfsg-7ubuntu0.1 Candidate: 9.54.0~dfsg1-0ubuntu2 Version table: 9.54.0~dfsg1-0ubuntu2 500 500 http://bg.archive.ubuntu.com/ubuntu impish/main amd64 Packages 500 http://bg.archive.ubuntu.com/ubuntu impish/main i386 Packages *** 9.53.3~dfsg-7ubuntu0.1 100 100 /var/lib/dpkg/status -- 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/1945645 Title: cups-pdf prints blank pages Status in cups package in Ubuntu: Confirmed Status in cups-pdf package in Ubuntu: Confirmed Status in ghostscript package in Ubuntu: Confirmed Status in ghostscript package in Debian: New Bug description: after updating from ubuntu 21.04 to ubuntu 21.10 the virtual pdf printer started to print blank pages (to create washed pdf files) printer-driver-cups-pdf, version 3.0.1-10 Description:Ubuntu Impish Indri (development branch) Release:21.10 printer-driver-cups-pdf: Installed: 3.0.1-10 Candidate: 3.0.1-10 Version table: *** 3.0.1-10 500 500 http://bg.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: printer-driver-cups-pdf 3.0.1-10 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 30 15:56:51 2021 InstallationDate: Installed on 2020-03-17 (561 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200205) Lpstat: device for PDF: cups-pdf:/ Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied SourcePackage: cups-pdf UpgradeStatus: Upgraded to impish on 2021-09-28 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1945645/+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 1945852] [NEW] sound strange noise - pulseaudio
Public bug reported: The sound from the speakers and headphones is distorted when the system startup. Has some strange disturbance in sound. If I issue "pulseausio -k; pulseaudio --start" the sound is correct but when another startup problem is come back. Reinstalling pulseaudio and alsa does not help. Actually my pulseaudio version is 1:13.99.1-1ubuntu3.11. I try under ubuntu 20.04.3 LTS and 21.04 but it is the same bug. Installing another newer kernel doesn't help either. The card is HDA Intel PCH, Cirrus Logic CS8409 / CS42L42 chip (Dell Vostro 3500). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bartek 3166 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 2 09:02:58 2021 InstallationDate: Installed on 2021-10-02 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2021 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0GGCMJ dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3500:pvr:sku0A24:rvnDellInc.:rn0GGCMJ:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3500 dmi.product.sku: 0A24 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1945852 Title: sound strange noise - pulseaudio Status in pulseaudio package in Ubuntu: New Bug description: The sound from the speakers and headphones is distorted when the system startup. Has some strange disturbance in sound. If I issue "pulseausio -k; pulseaudio --start" the sound is correct but when another startup problem is come back. Reinstalling pulseaudio and alsa does not help. Actually my pulseaudio version is 1:13.99.1-1ubuntu3.11. I try under ubuntu 20.04.3 LTS and 21.04 but it is the same bug. Installing another newer kernel doesn't help either. The card is HDA Intel PCH, Cirrus Logic CS8409 / CS42L42 chip (Dell Vostro 3500). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bartek 3166 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 2 09:02:58 2021 InstallationDate: Installed on 2021-10-02 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2021 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0GGCMJ dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3500:pvr:sku0A24:rvnDellInc.:rn0GGCMJ:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3500 dmi.product.sku: 0A24 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1945852/+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 1945851] [NEW] package cpio 2.13+dfsg-4ubuntu0.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: Was trying to install something and got this error but I don't really know how can i tell more about ProblemType: Package DistroRelease: Ubuntu 21.04 Package: cpio 2.13+dfsg-4ubuntu0.3 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 AptOrdering: gdebi-core:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Oct 2 09:23:50 2021 DuplicateSignature: package:cpio:2.13+dfsg-4ubuntu0.3 Unpacking gdebi-core (0.9.5.7+nmu4) ... dpkg: error processing package cpio (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2021-10-01 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RebootRequiredPkgs: evolution-data-server gnome-shell RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.4ubuntu0.1 SourcePackage: cpio Title: package cpio 2.13+dfsg-4ubuntu0.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cpio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package hirsute need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cpio in Ubuntu. https://bugs.launchpad.net/bugs/1945851 Title: package cpio 2.13+dfsg-4ubuntu0.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in cpio package in Ubuntu: New Bug description: Was trying to install something and got this error but I don't really know how can i tell more about ProblemType: Package DistroRelease: Ubuntu 21.04 Package: cpio 2.13+dfsg-4ubuntu0.3 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 AptOrdering: gdebi-core:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Oct 2 09:23:50 2021 DuplicateSignature: package:cpio:2.13+dfsg-4ubuntu0.3 Unpacking gdebi-core (0.9.5.7+nmu4) ... dpkg: error processing package cpio (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2021-10-01 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RebootRequiredPkgs: evolution-data-server gnome-shell RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.4ubuntu0.1 SourcePackage: cpio Title: package cpio 2.13+dfsg-4ubuntu0.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpio/+bug/1945851/+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 1923052] Re: screen reader does not read ubiquity window
Impish is still affected, tested on Ubuntu-MATE 21.10 "Impish Indri" - Beta amd64 (20211002) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1923052 Title: screen reader does not read ubiquity window Status in at-spi2-core package in Ubuntu: Confirmed Status in orca package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Run Ubuntu MATE 21.04 installation media 2. Try to follow http://iso.qa.ubuntu.com/qatracker/testcases/1309/info testcase by pressing ++ to activate screenreader with shown Ubiquity window, press to select some button Expected result: * screen reader reads ubiquity window Actual result: * screen reader does not read ubiquity window Note: screen reader actually works, it reads other windows - for example the terminal opened by ++. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.14 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 Date: Thu Apr 8 13:01:30 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210407.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1923052/+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 1945645] Re: cups-pdf prints blank pages
As a quick test, can you check if downgrading ghostscript (ghostscript, libgs9, libgs9-common) to the previous version fixes it or not? -- 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/1945645 Title: cups-pdf prints blank pages Status in cups package in Ubuntu: Confirmed Status in cups-pdf package in Ubuntu: Confirmed Status in ghostscript package in Ubuntu: Confirmed Status in ghostscript package in Debian: New Bug description: after updating from ubuntu 21.04 to ubuntu 21.10 the virtual pdf printer started to print blank pages (to create washed pdf files) printer-driver-cups-pdf, version 3.0.1-10 Description:Ubuntu Impish Indri (development branch) Release:21.10 printer-driver-cups-pdf: Installed: 3.0.1-10 Candidate: 3.0.1-10 Version table: *** 3.0.1-10 500 500 http://bg.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: printer-driver-cups-pdf 3.0.1-10 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 30 15:56:51 2021 InstallationDate: Installed on 2020-03-17 (561 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200205) Lpstat: device for PDF: cups-pdf:/ Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied SourcePackage: cups-pdf UpgradeStatus: Upgraded to impish on 2021-09-28 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1945645/+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 1772859] Re: Network Manager is not able to manage the devices on Ubuntu 18.04
While working on a remote server, it took me 2-3 hours to locate this bug report and apply its workarounds. It's certainly not a good default behavior. In case someone has already removed netplan, the recommended steps to get network-manager to manage the interfaces, as I understood them, are: ``` sudo -i apt install ubuntu-minimal echo "# Let NetworkManager manage all devices on this system network: version: 2 renderer: NetworkManager" >/etc/netplan/01-network-manager-all.yaml update-initramfs -u # Not sure if this is needed or not reboot ``` I.e. I think that /etc/netplan/01-network-manager-all.yaml comes from some installer and it's not part of some package and it needs to be manually re-created. -- 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/1772859 Title: Network Manager is not able to manage the devices on Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Invalid Status in network-manager package in Ubuntu: Invalid Bug description: NetworkManager is not able to manage the devices on latest Ubuntu(18.04) ---uname output--- Linux (none) 4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:36:36 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = z14 s390 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Install the latest Ubuntu(18.04) with Network Manager(1.10.4). 2. Configure a network device and login to the partition through ssh. 3. Now you can see the following output root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- Userspace tool common name: 1.10.6-2ubuntu1: amd64 arm64 armhf i386 ppc64el s390x The userspace tool has the following bit modes: 64-bit Userspace rpm: NetworkManager --version 1.10.4 Userspace tool obtained from project website: na Some more information about the issue: Network device has been configured manually after the image is up from Support Element(SE): - znetconf -a - cat /sys/bus/ccwgroup/drivers/qeth//if_name - ifconfig netmask 255.255.255.0 - route add default gw - SSH service has been configured This helped us to login to the Lpar. In Lpar - output of znetconf -c Device IDs TypeCard Type CHPID Drv. Name State - 0.0.1a80,0.0.1a81,0.0.1a82 1731/01 OSD_10GIG A8 qeth eth0 online 0.0.1810,0.0.1811,0.0.1812 1731/01 OSD_1000 D0 qeth eth1 online - output of nmcli c s root@(none):~# nmcli c s NAME UUID TYPE DEVICE - output of nmcli d s root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- * The above output shows that devices are not managed by nmcli After some investigation we found couple of suggestions like 1. Ubuntu(version <17.04): Creating an empty file(/etc/NetworkManager/conf.d/10-globally-managed-devices.conf) and restarting NM, solved the issue. 2. Ubuntu(version 17.10): Copying the said file(10-globally-managed-devices.conf) from /usr/lib to /etc/ and modifying the "unmanaged-devices" to none, resolved the issue. * link for reference: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842 For the latest version(18.04), none of the above solutions worked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1772859/+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
