Re: [Bug 2068738] verification-done-jammy-
Yes this kernel update did the trick after running the sudo update-grub command from my Ubuntu software and then going back into my Mint software. Thanks Linux team. Ralph Goe Sent with Proton Mail secure email. On Wednesday, July 17th, 2024 at 11:29 PM, Ubuntu Kernel Bot <2068...@bugs.launchpad.net> wrote: > This bug is awaiting verification that the linux-aws/5.15.0-1066.72 > kernel in -proposed solves the problem. Please test the kernel and > update this bug with the results. If the problem is solved, change the > tag 'verification-needed-jammy-linux-aws' to 'verification-done-jammy- > linux-aws'. If the problem still exists, change the tag 'verification- > needed-jammy-linux-aws' to 'verification-failed-jammy-linux-aws'. > > > If verification is not done by 5 working days from today, this fix will > be dropped from the source code, and this bug will be closed. > > > See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how > to enable and use -proposed. Thank you! > > > ** Tags added: kernel-spammed-jammy-linux-aws-v2 > verification-needed-jammy-linux-aws > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (2069485). > https://bugs.launchpad.net/bugs/2068738 > > Title: > AMD GPUs fail with null pointer dereference when IOMMU enabled, > leading to black screen > > Status in linux package in Ubuntu: > Fix Released > Status in linux source package in Jammy: > Fix Released > > Bug description: > BugLink: https://bugs.launchpad.net/bugs/2068738 > > [Impact] > > On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is > enabled, the system fails to boot correctly, and all users see is a > black screen. > > This is caused by a null pointer dereference when enabling the IOMMU > after the device has been initialised. It should happen the other way > around. > > AMD-Vi: AMD IOMMUv2 loaded and initialized > ... > amdgpu: Topology: Add APU node [0x15d8:0x1002] > kfd kfd: amdgpu: added device 1002:15d8 > kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8 > ... > amdgpu :06:00.0: amdgpu: amdgpu_device_ip_init failed > amdgpu :06:00.0: amdgpu: Fatal error during GPU init > amdgpu :06:00.0: amdgpu: amdgpu: finishing device. > ... > BUG: kernel NULL pointer dereference, address: 013c > ... > CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic #122-Ubuntu > ... > RIP: 0010:amdgpu_dm_fini+0x149/0x1f0 [amdgpu] > ... > Call Trace: > > > ? srso_return_thunk+0x5/0x10 > ? show_trace_log_lvl+0x28e/0x2ea > ? show_trace_log_lvl+0x28e/0x2ea > ? dm_hw_fini+0x23/0x30 [amdgpu] > ? show_regs.part.0+0x23/0x29 > ? __die_body.cold+0x8/0xd > ? __die+0x2b/0x37 > ? page_fault_oops+0x13b/0x170 > ? srso_return_thunk+0x5/0x10 > ? do_user_addr_fault+0x321/0x670 > ? srso_return_thunk+0x5/0x10 > ? __free_pages_ok+0x34a/0x4f0 > ? exc_page_fault+0x77/0x170 > ? asm_exc_page_fault+0x27/0x30 > ? amdgpu_dm_fini+0x149/0x1f0 [amdgpu] > dm_hw_fini+0x23/0x30 [amdgpu] > amdgpu_device_ip_fini_early.isra.0+0x278/0x312 [amdgpu] > amdgpu_device_fini_hw+0x156/0x208 [amdgpu] > amdgpu_driver_unload_kms+0x69/0x90 [amdgpu] > amdgpu_driver_load_kms.cold+0x81/0x107 [amdgpu] > amdgpu_pci_probe+0x1d1/0x290 [amdgpu] > local_pci_probe+0x4b/0x90 > ? srso_return_thunk+0x5/0x10 > pci_device_probe+0x119/0x200 > really_probe+0x222/0x420 > __driver_probe_device+0xe8/0x140 > driver_probe_device+0x23/0xc0 > __driver_attach+0xf7/0x1f0 > ? __device_attach_driver+0x140/0x140 > bus_for_each_dev+0x7f/0xd0 > driver_attach+0x1e/0x30 > bus_add_driver+0x148/0x220 > ? srso_return_thunk+0x5/0x10 > driver_register+0x95/0x100 > __pci_register_driver+0x68/0x70 > amdgpu_init+0x7c/0x1000 [amdgpu] > ? 0xc0e0b000 > do_one_initcall+0x49/0x1e0 > ? srso_return_thunk+0x5/0x10 > ? kmem_cache_alloc_trace+0x19e/0x2e0 > do_init_module+0x52/0x260 > load_module+0xb45/0xbe0 > __do_sys_finit_module+0xbf/0x120 > __x64_sys_finit_module+0x18/0x20 > x64_sys_call+0x1ac3/0x1fa0 > do_syscall_64+0x56/0xb0 > ... > entry_SYSCALL_64_after_hwframe+0x67/0xd1 > > A workaround does exist. Users can set "nomodeset" or "amd_iommu=off" > to GRUB_CMDLINE_LINUX_DEFAULT, update-grub and reboot. > > [Fix] > > The regression was caused by the following commit that landed in > 5.15.0-112-generic, and 5.15.150 upstream: > > commit 3c7e53c0d4b43ffe6e7715414b5f2b3177881ecd ubuntu-jammy > Author: Yifan Zhang yifan1.zh...@amd.com > > Date: Tue Sep 28 15:42:35 2021 +0800 > Subject: drm/amdgpu: init iommu after amdkfd device init > Link: > https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?id=3c7e53c0d4b43ffe6e7715414b5f2b3177881ecd > > The fix is to revert this patch, as it was not suppose to be > backported to 5.15 stable. > > The mailing list discussion with AMD developers is: > > https://lore.kernel.org/amd-gfx/20240523173031.4212-1-w_ar...@gmx.de/ > > The fix hasn't been acknowledged by Greg KH or Sasha Levin yet, so > sending as a Ubuntu
Re: [Bug 2068738] verification-failed-jammy-linux-azure
Hello Erv, Just wanted you to know what I did and found out. I tried the update grub command when I was in Linux mint OS, it did not have any effect. Then I remembered reading somebody else has the same issue, no effect until they went into something else on their computer, it had 3-4 letters, I didn't understand, they said the update worked from there because they had loader that software before their Mint software. So since I used to use UBUNTU, and still have it on my computer, before I loaded Mint, I figured I'd open my UBUNTU software and run the update grub command, then went back into Mint and it worked, I am now running 116 Kernel update. Good news, but my computer still shows that it cannot find that "boot" file, not sure but then I load the "next volume" and then I can choose to run either Windows, Ubuntu or Mint, so I'm good. Thanks for your attempt to help Erv. Ralph Goe Sent with Proton Mail secure email. On Thursday, July 18th, 2024 at 9:58 PM, Erv Bendiks <2068...@bugs.launchpad.net> wrote: > @RogerRamjet> Do you have motherboard,CPU and OS information to share? > > > > On Thu, Jul 18, 2024 at 6:45 PM Roger Ramjet 2068...@bugs.launchpad.net > > wrote: > > > Why does the updated kernel show installed but not active, I'm still > > having a problem? > > > > Sent with Proton Mail secure email. > > > > On Thursday, July 18th, 2024 at 2:47 PM, Pete Orlando > > 2068...@bugs.launchpad.net wrote: > > > > > Ok Black screen now fixed after "update Manger" sent new update on > > > 7/17/2024. Thank You Linux team ! > > > > > > On Thu, Jul 18, 2024 at 3:15 AM Roger Ramjet 2068...@bugs.launchpad.net > > > > > > wrote: > > > > > > > Unfortunately, I still have the same problem, after updating, I power > > > > down > > > > and restart, I get: > > > > error: file `/boot/' not found. > > > > > > > > I view the Kernels in the update manager, it shows 5.15.0-116 is > > > > "installed" and "supported until April 2027" > > > > > > > > The Kernel is loaded and installed but "not found" > > > > Then another window opens and I must choose "Boot from next volume" > > > > Then another window where I'm given the choice of booting from > > > > 5.15.0-107-generic (on /dev/sda5) > > > > This new Kernel is not listed at this window, not sure why not, seems > > > > it > > > > should be. > > > > > > > > If I can give you more info. let me know. > > > > > > > > Ralph Goe > > > > > > > > Sent with Proton Mail secure email. > > > > > > > > On Monday, July 15th, 2024 at 11:38 PM, Ubuntu Kernel Bot > > > > 2068...@bugs.launchpad.net wrote: > > > > > > > > > This bug is awaiting verification that the linux-azure/5.15.0-1069.78 > > > > > kernel in -proposed solves the problem. Please test the kernel and > > > > > update this bug with the results. If the problem is solved, change > > > > > the > > > > > tag 'verification-needed-jammy-linux-azure' to > > > > > 'verification-done-jammy- > > > > > linux-azure'. If the problem still exists, change the tag > > > > > 'verification- > > > > > needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'. > > > > > > > > > > If verification is not done by 5 working days from today, this fix > > > > > will > > > > > be dropped from the source code, and this bug will be closed. > > > > > > > > > > See https://wiki.ubuntu.com/Testing/EnableProposed for > > > > > documentation how > > > > > to enable and use -proposed. Thank you! > > > > > > > > > > ** Tags added: kernel-spammed-jammy-linux-azure-v2 > > > > > verification-needed-jammy-linux-azure > > > > > > > > > > -- > > > > > You received this bug notification because you are subscribed to a > > > > > duplicate bug report (2069485). > > > > > https://bugs.launchpad.net/bugs/2068738 > > > > > > > > > > Title: > > > > > AMD GPUs fail with null pointer dereference when IOMMU enabled, > > > > > leading to black screen > > > > > > > > > > Status in linux package in Ubuntu: > > > > > Fix Released > > > > > St
Re: [Bug 2068738] verification-failed-jammy-linux-azure
I noticed when the new update Kernel was loading this information, don't know if it will help... Thanks again, Ralph Sent with Proton Mail secure email. On Thursday, July 18th, 2024 at 9:58 PM, Erv Bendiks <2068...@bugs.launchpad.net> wrote: > @RogerRamjet> Do you have motherboard,CPU and OS information to share? > > > > On Thu, Jul 18, 2024 at 6:45 PM Roger Ramjet 2068...@bugs.launchpad.net > > wrote: > > > Why does the updated kernel show installed but not active, I'm still > > having a problem? > > > > Sent with Proton Mail secure email. > > > > On Thursday, July 18th, 2024 at 2:47 PM, Pete Orlando > > 2068...@bugs.launchpad.net wrote: > > > > > Ok Black screen now fixed after "update Manger" sent new update on > > > 7/17/2024. Thank You Linux team ! > > > > > > On Thu, Jul 18, 2024 at 3:15 AM Roger Ramjet 2068...@bugs.launchpad.net > > > > > > wrote: > > > > > > > Unfortunately, I still have the same problem, after updating, I power > > > > down > > > > and restart, I get: > > > > error: file `/boot/' not found. > > > > > > > > I view the Kernels in the update manager, it shows 5.15.0-116 is > > > > "installed" and "supported until April 2027" > > > > > > > > The Kernel is loaded and installed but "not found" > > > > Then another window opens and I must choose "Boot from next volume" > > > > Then another window where I'm given the choice of booting from > > > > 5.15.0-107-generic (on /dev/sda5) > > > > This new Kernel is not listed at this window, not sure why not, seems > > > > it > > > > should be. > > > > > > > > If I can give you more info. let me know. > > > > > > > > Ralph Goe > > > > > > > > Sent with Proton Mail secure email. > > > > > > > > On Monday, July 15th, 2024 at 11:38 PM, Ubuntu Kernel Bot > > > > 2068...@bugs.launchpad.net wrote: > > > > > > > > > This bug is awaiting verification that the linux-azure/5.15.0-1069.78 > > > > > kernel in -proposed solves the problem. Please test the kernel and > > > > > update this bug with the results. If the problem is solved, change > > > > > the > > > > > tag 'verification-needed-jammy-linux-azure' to > > > > > 'verification-done-jammy- > > > > > linux-azure'. If the problem still exists, change the tag > > > > > 'verification- > > > > > needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'. > > > > > > > > > > If verification is not done by 5 working days from today, this fix > > > > > will > > > > > be dropped from the source code, and this bug will be closed. > > > > > > > > > > See https://wiki.ubuntu.com/Testing/EnableProposed for > > > > > documentation how > > > > > to enable and use -proposed. Thank you! > > > > > > > > > > ** Tags added: kernel-spammed-jammy-linux-azure-v2 > > > > > verification-needed-jammy-linux-azure > > > > > > > > > > -- > > > > > You received this bug notification because you are subscribed to a > > > > > duplicate bug report (2069485). > > > > > https://bugs.launchpad.net/bugs/2068738 > > > > > > > > > > Title: > > > > > AMD GPUs fail with null pointer dereference when IOMMU enabled, > > > > > leading to black screen > > > > > > > > > > Status in linux package in Ubuntu: > > > > > Fix Released > > > > > Status in linux source package in Jammy: > > > > > Fix Released > > > > > > > > > > Bug description: > > > > > BugLink: https://bugs.launchpad.net/bugs/2068738 > > > > > > > > > > [Impact] > > > > > > > > > > On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is > > > > > enabled, the system fails to boot correctly, and all users see is a > > > > > black screen. > > > > > > > > > > This is caused by a null pointer dereference when enabling the IOMMU > > > > > after the device has been initialised. It should happen the other way > > > > > around. > > > > > >
Re: [Bug 2068738] verification-failed-jammy-linux-azure
Good morning, Yes I do, file is attached. Thanks, Ralph Goe Sent with Proton Mail secure email. On Thursday, July 18th, 2024 at 9:58 PM, Erv Bendiks <2068...@bugs.launchpad.net> wrote: > @RogerRamjet> Do you have motherboard,CPU and OS information to share? > > > > On Thu, Jul 18, 2024 at 6:45 PM Roger Ramjet 2068...@bugs.launchpad.net > > wrote: > > > Why does the updated kernel show installed but not active, I'm still > > having a problem? > > > > Sent with Proton Mail secure email. > > > > On Thursday, July 18th, 2024 at 2:47 PM, Pete Orlando > > 2068...@bugs.launchpad.net wrote: > > > > > Ok Black screen now fixed after "update Manger" sent new update on > > > 7/17/2024. Thank You Linux team ! > > > > > > On Thu, Jul 18, 2024 at 3:15 AM Roger Ramjet 2068...@bugs.launchpad.net > > > > > > wrote: > > > > > > > Unfortunately, I still have the same problem, after updating, I power > > > > down > > > > and restart, I get: > > > > error: file `/boot/' not found. > > > > > > > > I view the Kernels in the update manager, it shows 5.15.0-116 is > > > > "installed" and "supported until April 2027" > > > > > > > > The Kernel is loaded and installed but "not found" > > > > Then another window opens and I must choose "Boot from next volume" > > > > Then another window where I'm given the choice of booting from > > > > 5.15.0-107-generic (on /dev/sda5) > > > > This new Kernel is not listed at this window, not sure why not, seems > > > > it > > > > should be. > > > > > > > > If I can give you more info. let me know. > > > > > > > > Ralph Goe > > > > > > > > Sent with Proton Mail secure email. > > > > > > > > On Monday, July 15th, 2024 at 11:38 PM, Ubuntu Kernel Bot > > > > 2068...@bugs.launchpad.net wrote: > > > > > > > > > This bug is awaiting verification that the linux-azure/5.15.0-1069.78 > > > > > kernel in -proposed solves the problem. Please test the kernel and > > > > > update this bug with the results. If the problem is solved, change > > > > > the > > > > > tag 'verification-needed-jammy-linux-azure' to > > > > > 'verification-done-jammy- > > > > > linux-azure'. If the problem still exists, change the tag > > > > > 'verification- > > > > > needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'. > > > > > > > > > > If verification is not done by 5 working days from today, this fix > > > > > will > > > > > be dropped from the source code, and this bug will be closed. > > > > > > > > > > See https://wiki.ubuntu.com/Testing/EnableProposed for > > > > > documentation how > > > > > to enable and use -proposed. Thank you! > > > > > > > > > > ** Tags added: kernel-spammed-jammy-linux-azure-v2 > > > > > verification-needed-jammy-linux-azure > > > > > > > > > > -- > > > > > You received this bug notification because you are subscribed to a > > > > > duplicate bug report (2069485). > > > > > https://bugs.launchpad.net/bugs/2068738 > > > > > > > > > > Title: > > > > > AMD GPUs fail with null pointer dereference when IOMMU enabled, > > > > > leading to black screen > > > > > > > > > > Status in linux package in Ubuntu: > > > > > Fix Released > > > > > Status in linux source package in Jammy: > > > > > Fix Released > > > > > > > > > > Bug description: > > > > > BugLink: https://bugs.launchpad.net/bugs/2068738 > > > > > > > > > > [Impact] > > > > > > > > > > On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is > > > > > enabled, the system fails to boot correctly, and all users see is a > > > > > black screen. > > > > > > > > > > This is caused by a null pointer dereference when enabling the IOMMU > > > > > after the device has been initialised. It should happen the other way > > > > > around. > > > > > > > > > > AMD-Vi: AMD IOMMUv2
Re: [Bug 2068738] verification-failed-jammy-linux-azure
Why does the updated kernel show installed but not active, I'm still having a problem? Sent with Proton Mail secure email. On Thursday, July 18th, 2024 at 2:47 PM, Pete Orlando <2068...@bugs.launchpad.net> wrote: > Ok Black screen now fixed after "update Manger" sent new update on > 7/17/2024. Thank You Linux team ! > > > On Thu, Jul 18, 2024 at 3:15 AM Roger Ramjet 2068...@bugs.launchpad.net > > wrote: > > > Unfortunately, I still have the same problem, after updating, I power down > > and restart, I get: > > error: file `/boot/' not found. > > > > I view the Kernels in the update manager, it shows 5.15.0-116 is > > "installed" and "supported until April 2027" > > > > The Kernel is loaded and installed but "not found" > > Then another window opens and I must choose "Boot from next volume" > > Then another window where I'm given the choice of booting from > > 5.15.0-107-generic (on /dev/sda5) > > This new Kernel is not listed at this window, not sure why not, seems it > > should be. > > > > If I can give you more info. let me know. > > > > Ralph Goe > > > > Sent with Proton Mail secure email. > > > > On Monday, July 15th, 2024 at 11:38 PM, Ubuntu Kernel Bot > > 2068...@bugs.launchpad.net wrote: > > > > > This bug is awaiting verification that the linux-azure/5.15.0-1069.78 > > > kernel in -proposed solves the problem. Please test the kernel and > > > update this bug with the results. If the problem is solved, change the > > > tag 'verification-needed-jammy-linux-azure' to 'verification-done-jammy- > > > linux-azure'. If the problem still exists, change the tag 'verification- > > > needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'. > > > > > > If verification is not done by 5 working days from today, this fix will > > > be dropped from the source code, and this bug will be closed. > > > > > > See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how > > > to enable and use -proposed. Thank you! > > > > > > ** Tags added: kernel-spammed-jammy-linux-azure-v2 > > > verification-needed-jammy-linux-azure > > > > > > -- > > > You received this bug notification because you are subscribed to a > > > duplicate bug report (2069485). > > > https://bugs.launchpad.net/bugs/2068738 > > > > > > Title: > > > AMD GPUs fail with null pointer dereference when IOMMU enabled, > > > leading to black screen > > > > > > Status in linux package in Ubuntu: > > > Fix Released > > > Status in linux source package in Jammy: > > > Fix Released > > > > > > Bug description: > > > BugLink: https://bugs.launchpad.net/bugs/2068738 > > > > > > [Impact] > > > > > > On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is > > > enabled, the system fails to boot correctly, and all users see is a > > > black screen. > > > > > > This is caused by a null pointer dereference when enabling the IOMMU > > > after the device has been initialised. It should happen the other way > > > around. > > > > > > AMD-Vi: AMD IOMMUv2 loaded and initialized > > > ... > > > amdgpu: Topology: Add APU node [0x15d8:0x1002] > > > kfd kfd: amdgpu: added device 1002:15d8 > > > kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8 > > > ... > > > amdgpu :06:00.0: amdgpu: amdgpu_device_ip_init failed > > > amdgpu :06:00.0: amdgpu: Fatal error during GPU init > > > amdgpu :06:00.0: amdgpu: amdgpu: finishing device. > > > ... > > > BUG: kernel NULL pointer dereference, address: 013c > > > ... > > > CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic > > > #122-Ubuntu > > > ... > > > RIP: 0010:amdgpu_dm_fini+0x149/0x1f0 [amdgpu] > > > ... > > > Call Trace: > > > > > > > > > ? srso_return_thunk+0x5/0x10 > > > ? show_trace_log_lvl+0x28e/0x2ea > > > ? show_trace_log_lvl+0x28e/0x2ea > > > ? dm_hw_fini+0x23/0x30 [amdgpu] > > > ? show_regs.part.0+0x23/0x29 > > > ? __die_body.cold+0x8/0xd > > > ? __die+0x2b/0x37 > > > ? page_fault_oops+0x13b/0x170 > > > ? srso_return_thunk+0x5/0x10 > > > ? do_user_addr_fault+0x321/0x670 > > > ? srso_return_thunk+0x5/0x10 > > > ? __free_pages_ok+0x34a/0x4
[Bug 2068738] verification-failed-jammy-linux-azure
Unfortunately, I still have the same problem, after updating, I power down and restart, I get: error: file `/boot/' not found. I view the Kernels in the update manager, it shows 5.15.0-116 is "installed" and "supported until April 2027" The Kernel is loaded and installed but "not found" Then another window opens and I must choose "Boot from next volume" Then another window where I'm given the choice of booting from 5.15.0-107-generic (on /dev/sda5) This new Kernel is not listed at this window, not sure why not, seems it should be. If I can give you more info. let me know. Ralph Goe Sent with Proton Mail secure email. On Monday, July 15th, 2024 at 11:38 PM, Ubuntu Kernel Bot <2068...@bugs.launchpad.net> wrote: > This bug is awaiting verification that the linux-azure/5.15.0-1069.78 > kernel in -proposed solves the problem. Please test the kernel and > update this bug with the results. If the problem is solved, change the > tag 'verification-needed-jammy-linux-azure' to 'verification-done-jammy- > linux-azure'. If the problem still exists, change the tag 'verification- > needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'. > > > If verification is not done by 5 working days from today, this fix will > be dropped from the source code, and this bug will be closed. > > > See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how > to enable and use -proposed. Thank you! > > > ** Tags added: kernel-spammed-jammy-linux-azure-v2 > verification-needed-jammy-linux-azure > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (2069485). > https://bugs.launchpad.net/bugs/2068738 > > Title: > AMD GPUs fail with null pointer dereference when IOMMU enabled, > leading to black screen > > Status in linux package in Ubuntu: > Fix Released > Status in linux source package in Jammy: > Fix Released > > Bug description: > BugLink: https://bugs.launchpad.net/bugs/2068738 > > [Impact] > > On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is > enabled, the system fails to boot correctly, and all users see is a > black screen. > > This is caused by a null pointer dereference when enabling the IOMMU > after the device has been initialised. It should happen the other way > around. > > AMD-Vi: AMD IOMMUv2 loaded and initialized > ... > amdgpu: Topology: Add APU node [0x15d8:0x1002] > kfd kfd: amdgpu: added device 1002:15d8 > kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8 > ... > amdgpu :06:00.0: amdgpu: amdgpu_device_ip_init failed > amdgpu :06:00.0: amdgpu: Fatal error during GPU init > amdgpu :06:00.0: amdgpu: amdgpu: finishing device. > ... > BUG: kernel NULL pointer dereference, address: 013c > ... > CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic #122-Ubuntu > ... > RIP: 0010:amdgpu_dm_fini+0x149/0x1f0 [amdgpu] > ... > Call Trace: > > > ? srso_return_thunk+0x5/0x10 > ? show_trace_log_lvl+0x28e/0x2ea > ? show_trace_log_lvl+0x28e/0x2ea > ? dm_hw_fini+0x23/0x30 [amdgpu] > ? show_regs.part.0+0x23/0x29 > ? __die_body.cold+0x8/0xd > ? __die+0x2b/0x37 > ? page_fault_oops+0x13b/0x170 > ? srso_return_thunk+0x5/0x10 > ? do_user_addr_fault+0x321/0x670 > ? srso_return_thunk+0x5/0x10 > ? __free_pages_ok+0x34a/0x4f0 > ? exc_page_fault+0x77/0x170 > ? asm_exc_page_fault+0x27/0x30 > ? amdgpu_dm_fini+0x149/0x1f0 [amdgpu] > dm_hw_fini+0x23/0x30 [amdgpu] > amdgpu_device_ip_fini_early.isra.0+0x278/0x312 [amdgpu] > amdgpu_device_fini_hw+0x156/0x208 [amdgpu] > amdgpu_driver_unload_kms+0x69/0x90 [amdgpu] > amdgpu_driver_load_kms.cold+0x81/0x107 [amdgpu] > amdgpu_pci_probe+0x1d1/0x290 [amdgpu] > local_pci_probe+0x4b/0x90 > ? srso_return_thunk+0x5/0x10 > pci_device_probe+0x119/0x200 > really_probe+0x222/0x420 > __driver_probe_device+0xe8/0x140 > driver_probe_device+0x23/0xc0 > __driver_attach+0xf7/0x1f0 > ? __device_attach_driver+0x140/0x140 > bus_for_each_dev+0x7f/0xd0 > driver_attach+0x1e/0x30 > bus_add_driver+0x148/0x220 > ? srso_return_thunk+0x5/0x10 > driver_register+0x95/0x100 > __pci_register_driver+0x68/0x70 > amdgpu_init+0x7c/0x1000 [amdgpu] > ? 0xc0e0b000 > do_one_initcall+0x49/0x1e0 > ? srso_return_thunk+0x5/0x10 > ? kmem_cache_alloc_trace+0x19e/0x2e0 > do_init_module+0x52/0x260 > load_module+0xb45/0xbe0 > __do_sys_finit_module+0xbf/0x120 > __x64_sys_finit_module+0x18/0x20 > x64_sys_call+0x1ac3/0x1fa0 > do_syscall_64+0x56/0xb0 > ... > entry_SYSCALL_64_after_hwframe+0x67/0xd1 > > A workaround does exist. Users can set "nomodeset" or "amd_iommu=off" > to GRUB_CMDLINE_LINUX_DEFAULT, update-grub and reboot. > > [Fix] > > The regression was caused by the following commit that landed in > 5.15.0-112-generic, and 5.15.150 upstream: > > commit 3c7e53c0d4b43ffe6e7715414b5f2b3177881ecd ubuntu-jammy > Author: Yifan Zhang yifan1.zh...@amd.com > > Date: Tue Sep 28 15:42:35 2021 +0800 > Subject: drm/amdgpu: init iommu after amdkfd device init > Link: >
[Bug 2068738] verification-needed-jammy-linux-bluefield
Unfortunately, I still have the same problem, after updating, I power down and restart, I get: error: file `/boot/' not found. I view the Kernels in the update manager, it shows 5.15.0-116 is "installed" and "supported until April 2027" The Kernel is loaded and installed but "not found" Then another window opens and I must choose "Boot from next volume" Then another window where I'm given the choice of booting from 5.15.0-107-generic (on /dev/sda5) This new Kernel is not listed at this window, not sure why not, seems it should be. If I can give you more info. let me know. Ralph Goe Sent with Proton Mail secure email. On Tuesday, July 16th, 2024 at 9:56 AM, Ubuntu Kernel Bot <2068...@bugs.launchpad.net> wrote: > This bug is awaiting verification that the linux-gke/5.15.0-1063.69 > kernel in -proposed solves the problem. Please test the kernel and > update this bug with the results. If the problem is solved, change the > tag 'verification-needed-jammy-linux-gke' to 'verification-done-jammy- > linux-gke'. If the problem still exists, change the tag 'verification- > needed-jammy-linux-gke' to 'verification-failed-jammy-linux-gke'. > > > If verification is not done by 5 working days from today, this fix will > be dropped from the source code, and this bug will be closed. > > > See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how > to enable and use -proposed. Thank you! > > > ** Tags added: kernel-spammed-jammy-linux-gke-v2 > verification-needed-jammy-linux-gke > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (2069485). > https://bugs.launchpad.net/bugs/2068738 > > Title: > AMD GPUs fail with null pointer dereference when IOMMU enabled, > leading to black screen > > Status in linux package in Ubuntu: > Fix Released > Status in linux source package in Jammy: > Fix Released > > Bug description: > BugLink: https://bugs.launchpad.net/bugs/2068738 > > [Impact] > > On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is > enabled, the system fails to boot correctly, and all users see is a > black screen. > > This is caused by a null pointer dereference when enabling the IOMMU > after the device has been initialised. It should happen the other way > around. > > AMD-Vi: AMD IOMMUv2 loaded and initialized > ... > amdgpu: Topology: Add APU node [0x15d8:0x1002] > kfd kfd: amdgpu: added device 1002:15d8 > kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8 > ... > amdgpu :06:00.0: amdgpu: amdgpu_device_ip_init failed > amdgpu :06:00.0: amdgpu: Fatal error during GPU init > amdgpu :06:00.0: amdgpu: amdgpu: finishing device. > ... > BUG: kernel NULL pointer dereference, address: 013c > ... > CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic #122-Ubuntu > ... > RIP: 0010:amdgpu_dm_fini+0x149/0x1f0 [amdgpu] > ... > Call Trace: > > > ? srso_return_thunk+0x5/0x10 > ? show_trace_log_lvl+0x28e/0x2ea > ? show_trace_log_lvl+0x28e/0x2ea > ? dm_hw_fini+0x23/0x30 [amdgpu] > ? show_regs.part.0+0x23/0x29 > ? __die_body.cold+0x8/0xd > ? __die+0x2b/0x37 > ? page_fault_oops+0x13b/0x170 > ? srso_return_thunk+0x5/0x10 > ? do_user_addr_fault+0x321/0x670 > ? srso_return_thunk+0x5/0x10 > ? __free_pages_ok+0x34a/0x4f0 > ? exc_page_fault+0x77/0x170 > ? asm_exc_page_fault+0x27/0x30 > ? amdgpu_dm_fini+0x149/0x1f0 [amdgpu] > dm_hw_fini+0x23/0x30 [amdgpu] > amdgpu_device_ip_fini_early.isra.0+0x278/0x312 [amdgpu] > amdgpu_device_fini_hw+0x156/0x208 [amdgpu] > amdgpu_driver_unload_kms+0x69/0x90 [amdgpu] > amdgpu_driver_load_kms.cold+0x81/0x107 [amdgpu] > amdgpu_pci_probe+0x1d1/0x290 [amdgpu] > local_pci_probe+0x4b/0x90 > ? srso_return_thunk+0x5/0x10 > pci_device_probe+0x119/0x200 > really_probe+0x222/0x420 > __driver_probe_device+0xe8/0x140 > driver_probe_device+0x23/0xc0 > __driver_attach+0xf7/0x1f0 > ? __device_attach_driver+0x140/0x140 > bus_for_each_dev+0x7f/0xd0 > driver_attach+0x1e/0x30 > bus_add_driver+0x148/0x220 > ? srso_return_thunk+0x5/0x10 > driver_register+0x95/0x100 > __pci_register_driver+0x68/0x70 > amdgpu_init+0x7c/0x1000 [amdgpu] > ? 0xc0e0b000 > do_one_initcall+0x49/0x1e0 > ? srso_return_thunk+0x5/0x10 > ? kmem_cache_alloc_trace+0x19e/0x2e0 > do_init_module+0x52/0x260 > load_module+0xb45/0xbe0 > __do_sys_finit_module+0xbf/0x120 > __x64_sys_finit_module+0x18/0x20 > x64_sys_call+0x1ac3/0x1fa0 > do_syscall_64+0x56/0xb0 > ... > entry_SYSCALL_64_after_hwframe+0x67/0xd1 > > A workaround does exist. Users can set "nomodeset" or "amd_iommu=off" > to GRUB_CMDLINE_LINUX_DEFAULT, update-grub and reboot. > > [Fix] > > The regression was caused by the following commit that landed in > 5.15.0-112-generic, and 5.15.150 upstream: > > commit 3c7e53c0d4b43ffe6e7715414b5f2b3177881ecd ubuntu-jammy > Author: Yifan Zhang yifan1.zh...@amd.com > > Date: Tue Sep 28 15:42:35 2021 +0800 > Subject: drm/amdgpu: init iommu after amdkfd device init > Link: >
[Bug 2068738] verification-needed-jammy-linux-bluefield
Unfortunately, I still have the same problem, after updating, I power down and restart, I get: error: file `/boot/' not found. I view the Kernels in the update manager, it shows 5.15.0-116 is "installed" and "supported until April 2027" The Kernel is loaded and installed but "not found" Then another window opens and I must choose "Boot from next volume" Then another window where I'm given the choice of booting from 5.15.0-107-generic (on /dev/sda5) This new Kernel is not listed at this window, not sure why not, seems it should be. If I can give you more info. let me know. Ralph Goe Sent with Proton Mail secure email. On Wednesday, July 17th, 2024 at 9:59 PM, Ubuntu Kernel Bot <2068...@bugs.launchpad.net> wrote: > This bug is awaiting verification that the linux- > bluefield/5.15.0-1048.50 kernel in -proposed solves the problem. Please > test the kernel and update this bug with the results. If the problem is > solved, change the tag 'verification-needed-jammy-linux-bluefield' to > 'verification-done-jammy-linux-bluefield'. If the problem still exists, > change the tag 'verification-needed-jammy-linux-bluefield' to > 'verification-failed-jammy-linux-bluefield'. > > > If verification is not done by 5 working days from today, this fix will > be dropped from the source code, and this bug will be closed. > > > See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how > to enable and use -proposed. Thank you! > > > ** Tags added: kernel-spammed-jammy-linux-bluefield-v2 > verification-needed-jammy-linux-bluefield > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (2069485). > https://bugs.launchpad.net/bugs/2068738 > > Title: > AMD GPUs fail with null pointer dereference when IOMMU enabled, > leading to black screen > > Status in linux package in Ubuntu: > Fix Released > Status in linux source package in Jammy: > Fix Released > > Bug description: > BugLink: https://bugs.launchpad.net/bugs/2068738 > > [Impact] > > On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is > enabled, the system fails to boot correctly, and all users see is a > black screen. > > This is caused by a null pointer dereference when enabling the IOMMU > after the device has been initialised. It should happen the other way > around. > > AMD-Vi: AMD IOMMUv2 loaded and initialized > ... > amdgpu: Topology: Add APU node [0x15d8:0x1002] > kfd kfd: amdgpu: added device 1002:15d8 > kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8 > ... > amdgpu :06:00.0: amdgpu: amdgpu_device_ip_init failed > amdgpu :06:00.0: amdgpu: Fatal error during GPU init > amdgpu :06:00.0: amdgpu: amdgpu: finishing device. > ... > BUG: kernel NULL pointer dereference, address: 013c > ... > CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic #122-Ubuntu > ... > RIP: 0010:amdgpu_dm_fini+0x149/0x1f0 [amdgpu] > ... > Call Trace: > > > ? srso_return_thunk+0x5/0x10 > ? show_trace_log_lvl+0x28e/0x2ea > ? show_trace_log_lvl+0x28e/0x2ea > ? dm_hw_fini+0x23/0x30 [amdgpu] > ? show_regs.part.0+0x23/0x29 > ? __die_body.cold+0x8/0xd > ? __die+0x2b/0x37 > ? page_fault_oops+0x13b/0x170 > ? srso_return_thunk+0x5/0x10 > ? do_user_addr_fault+0x321/0x670 > ? srso_return_thunk+0x5/0x10 > ? __free_pages_ok+0x34a/0x4f0 > ? exc_page_fault+0x77/0x170 > ? asm_exc_page_fault+0x27/0x30 > ? amdgpu_dm_fini+0x149/0x1f0 [amdgpu] > dm_hw_fini+0x23/0x30 [amdgpu] > amdgpu_device_ip_fini_early.isra.0+0x278/0x312 [amdgpu] > amdgpu_device_fini_hw+0x156/0x208 [amdgpu] > amdgpu_driver_unload_kms+0x69/0x90 [amdgpu] > amdgpu_driver_load_kms.cold+0x81/0x107 [amdgpu] > amdgpu_pci_probe+0x1d1/0x290 [amdgpu] > local_pci_probe+0x4b/0x90 > ? srso_return_thunk+0x5/0x10 > pci_device_probe+0x119/0x200 > really_probe+0x222/0x420 > __driver_probe_device+0xe8/0x140 > driver_probe_device+0x23/0xc0 > __driver_attach+0xf7/0x1f0 > ? __device_attach_driver+0x140/0x140 > bus_for_each_dev+0x7f/0xd0 > driver_attach+0x1e/0x30 > bus_add_driver+0x148/0x220 > ? srso_return_thunk+0x5/0x10 > driver_register+0x95/0x100 > __pci_register_driver+0x68/0x70 > amdgpu_init+0x7c/0x1000 [amdgpu] > ? 0xc0e0b000 > do_one_initcall+0x49/0x1e0 > ? srso_return_thunk+0x5/0x10 > ? kmem_cache_alloc_trace+0x19e/0x2e0 > do_init_module+0x52/0x260 > load_module+0xb45/0xbe0 > __do_sys_finit_module+0xbf/0x120 > __x64_sys_finit_module+0x18/0x20 > x64_sys_call+0x1ac3/0x1fa0 > do_syscall_64+0x56/0xb0 > ... > entry_SYSCALL_64_after_hwframe+0x67/0xd1 > > A workaround does exist. Users can set "nomodeset" or "amd_iommu=off" > to GRUB_CMDLINE_LINUX_DEFAULT, update-grub and reboot. > > [Fix] > > The regression was caused by the following commit that landed in > 5.15.0-112-generic, and 5.15.150 upstream: > > commit 3c7e53c0d4b43ffe6e7715414b5f2b3177881ecd ubuntu-jammy > Author: Yifan Zhang yifan1.zh...@amd.com > > Date: Tue Sep 28 15:42:35 2021 +0800 > Subject: drm/amdgpu: init iommu after amdkfd device init >
[Bug 2068738] verification-failed-jammy-linux-aws
Unfortunately, I still have the same problem, after updating, I power down and restart, I get: error: file `/boot/' not found. I view the Kernels in the update manager, it shows 5.15.0-116 is "installed" and "supported until April 2027" The Kernel is loaded and installed but "not found" Then another window opens and I must choose "Boot from next volume" Then another window where I'm given the choice of booting from 5.15.0-107-generic (on /dev/sda5) This new Kernel is not listed at this window, not sure why not, seems it should be. If I can give you more info. let me know. Ralph Goe Sent with Proton Mail secure email. On Wednesday, July 17th, 2024 at 11:29 PM, Ubuntu Kernel Bot <2068...@bugs.launchpad.net> wrote: > This bug is awaiting verification that the linux-aws/5.15.0-1066.72 > kernel in -proposed solves the problem. Please test the kernel and > update this bug with the results. If the problem is solved, change the > tag 'verification-needed-jammy-linux-aws' to 'verification-done-jammy- > linux-aws'. If the problem still exists, change the tag 'verification- > needed-jammy-linux-aws' to 'verification-failed-jammy-linux-aws'. > > > If verification is not done by 5 working days from today, this fix will > be dropped from the source code, and this bug will be closed. > > > See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how > to enable and use -proposed. Thank you! > > > ** Tags added: kernel-spammed-jammy-linux-aws-v2 > verification-needed-jammy-linux-aws > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (2069485). > https://bugs.launchpad.net/bugs/2068738 > > Title: > AMD GPUs fail with null pointer dereference when IOMMU enabled, > leading to black screen > > Status in linux package in Ubuntu: > Fix Released > Status in linux source package in Jammy: > Fix Released > > Bug description: > BugLink: https://bugs.launchpad.net/bugs/2068738 > > [Impact] > > On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is > enabled, the system fails to boot correctly, and all users see is a > black screen. > > This is caused by a null pointer dereference when enabling the IOMMU > after the device has been initialised. It should happen the other way > around. > > AMD-Vi: AMD IOMMUv2 loaded and initialized > ... > amdgpu: Topology: Add APU node [0x15d8:0x1002] > kfd kfd: amdgpu: added device 1002:15d8 > kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8 > ... > amdgpu :06:00.0: amdgpu: amdgpu_device_ip_init failed > amdgpu :06:00.0: amdgpu: Fatal error during GPU init > amdgpu :06:00.0: amdgpu: amdgpu: finishing device. > ... > BUG: kernel NULL pointer dereference, address: 013c > ... > CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic #122-Ubuntu > ... > RIP: 0010:amdgpu_dm_fini+0x149/0x1f0 [amdgpu] > ... > Call Trace: > > > ? srso_return_thunk+0x5/0x10 > ? show_trace_log_lvl+0x28e/0x2ea > ? show_trace_log_lvl+0x28e/0x2ea > ? dm_hw_fini+0x23/0x30 [amdgpu] > ? show_regs.part.0+0x23/0x29 > ? __die_body.cold+0x8/0xd > ? __die+0x2b/0x37 > ? page_fault_oops+0x13b/0x170 > ? srso_return_thunk+0x5/0x10 > ? do_user_addr_fault+0x321/0x670 > ? srso_return_thunk+0x5/0x10 > ? __free_pages_ok+0x34a/0x4f0 > ? exc_page_fault+0x77/0x170 > ? asm_exc_page_fault+0x27/0x30 > ? amdgpu_dm_fini+0x149/0x1f0 [amdgpu] > dm_hw_fini+0x23/0x30 [amdgpu] > amdgpu_device_ip_fini_early.isra.0+0x278/0x312 [amdgpu] > amdgpu_device_fini_hw+0x156/0x208 [amdgpu] > amdgpu_driver_unload_kms+0x69/0x90 [amdgpu] > amdgpu_driver_load_kms.cold+0x81/0x107 [amdgpu] > amdgpu_pci_probe+0x1d1/0x290 [amdgpu] > local_pci_probe+0x4b/0x90 > ? srso_return_thunk+0x5/0x10 > pci_device_probe+0x119/0x200 > really_probe+0x222/0x420 > __driver_probe_device+0xe8/0x140 > driver_probe_device+0x23/0xc0 > __driver_attach+0xf7/0x1f0 > ? __device_attach_driver+0x140/0x140 > bus_for_each_dev+0x7f/0xd0 > driver_attach+0x1e/0x30 > bus_add_driver+0x148/0x220 > ? srso_return_thunk+0x5/0x10 > driver_register+0x95/0x100 > __pci_register_driver+0x68/0x70 > amdgpu_init+0x7c/0x1000 [amdgpu] > ? 0xc0e0b000 > do_one_initcall+0x49/0x1e0 > ? srso_return_thunk+0x5/0x10 > ? kmem_cache_alloc_trace+0x19e/0x2e0 > do_init_module+0x52/0x260 > load_module+0xb45/0xbe0 > __do_sys_finit_module+0xbf/0x120 > __x64_sys_finit_module+0x18/0x20 > x64_sys_call+0x1ac3/0x1fa0 > do_syscall_64+0x56/0xb0 > ... > entry_SYSCALL_64_after_hwframe+0x67/0xd1 > > A workaround does exist. Users can set "nomodeset" or "amd_iommu=off" > to GRUB_CMDLINE_LINUX_DEFAULT, update-grub and reboot. > > [Fix] > > The regression was caused by the following commit that landed in > 5.15.0-112-generic, and 5.15.150 upstream: > > commit 3c7e53c0d4b43ffe6e7715414b5f2b3177881ecd ubuntu-jammy > Author: Yifan Zhang yifan1.zh...@amd.com > > Date: Tue Sep 28 15:42:35 2021 +0800 > Subject: drm/amdgpu: init iommu after amdkfd device init > Link: >
Re: [Bug 2068738] verification-failed-jammy-linux-gke
Why in my Update Manager when viewing the Kernels, 5.15.0-116 is shown as "Installed" but not "Active"? And when powering up I get: "error: file `/boot/' not found" Maybe this is the problem and not the new Kernel? Thanks, Ralph Sent with Proton Mail secure email. On Tuesday, July 16th, 2024 at 7:02 PM, Erv Bendiks <2068...@bugs.launchpad.net> wrote: > I just booted my AMD 3200G Linux Mint box with 5.15.0-116-generic and it > didn't hang with a blank screen. This box passed test. > > On Tue, Jul 16, 2024 at 11:00 AM Roger Ramjet 2068...@bugs.launchpad.net > > wrote: > > > Not sure if I'm replying correctly, this bug fix did not help me. > > > > Unfortunately, I still have the same problem, after updating, I power down > > and restart, I get: > > error: file `/boot/' not found. > > > > I view the Kernels in the update manager, it shows 5.15.0-116 is > > "installed" and "supported until April 2027" > > > > The Kernel is loaded and installed but "not found" > > Then another window opens and I must choose "Boot from next volume" > > Then another window where I'm given the choice of booting from > > 5.15.0-107-generic (on /dev/sda5) > > This new Kernel is not listed at this window, not sure why not, seems it > > should be. > > > > If I can give you more info. let me know. > > > > Ralph Goe > > > > Sent with Proton Mail secure email. > > > > On Tuesday, July 16th, 2024 at 9:56 AM, Ubuntu Kernel Bot > > 2068...@bugs.launchpad.net wrote: > > > > > This bug is awaiting verification that the linux-gke/5.15.0-1063.69 > > > kernel in -proposed solves the problem. Please test the kernel and > > > update this bug with the results. If the problem is solved, change the > > > tag 'verification-needed-jammy-linux-gke' to 'verification-done-jammy- > > > linux-gke'. If the problem still exists, change the tag 'verification- > > > needed-jammy-linux-gke' to 'verification-failed-jammy-linux-gke'. > > > > > > If verification is not done by 5 working days from today, this fix will > > > be dropped from the source code, and this bug will be closed. > > > > > > See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how > > > to enable and use -proposed. Thank you! > > > > > > ** Tags added: kernel-spammed-jammy-linux-gke-v2 > > > verification-needed-jammy-linux-gke > > > > > > -- > > > You received this bug notification because you are subscribed to a > > > duplicate bug report (2069485). > > > https://bugs.launchpad.net/bugs/2068738 > > > > > > Title: > > > AMD GPUs fail with null pointer dereference when IOMMU enabled, > > > leading to black screen > > > > > > Status in linux package in Ubuntu: > > > Fix Released > > > Status in linux source package in Jammy: > > > Fix Released > > > > > > Bug description: > > > BugLink: https://bugs.launchpad.net/bugs/2068738 > > > > > > [Impact] > > > > > > On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is > > > enabled, the system fails to boot correctly, and all users see is a > > > black screen. > > > > > > This is caused by a null pointer dereference when enabling the IOMMU > > > after the device has been initialised. It should happen the other way > > > around. > > > > > > AMD-Vi: AMD IOMMUv2 loaded and initialized > > > ... > > > amdgpu: Topology: Add APU node [0x15d8:0x1002] > > > kfd kfd: amdgpu: added device 1002:15d8 > > > kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8 > > > ... > > > amdgpu :06:00.0: amdgpu: amdgpu_device_ip_init failed > > > amdgpu :06:00.0: amdgpu: Fatal error during GPU init > > > amdgpu :06:00.0: amdgpu: amdgpu: finishing device. > > > ... > > > BUG: kernel NULL pointer dereference, address: 013c > > > ... > > > CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic > > > #122-Ubuntu > > > ... > > > RIP: 0010:amdgpu_dm_fini+0x149/0x1f0 [amdgpu] > > > ... > > > Call Trace: > > > > > > > > > ? srso_return_thunk+0x5/0x10 > > > ? show_trace_log_lvl+0x28e/0x2ea > > > ? show_trace_log_lvl+0x28e/0x2ea > > > ? dm_hw_fini+0x23/0x30 [amdgpu] > > > ? show_regs.part.0+0x23/0x29 > > > ? __die_body.
[Bug 2068738] verification-failed-jammy- linux-nvidia
Unfortunately, I still have the same problem, after updating, I power down and restart, I get: error: file `/boot/' not found. I view the Kernels in the update manager, it shows 5.15.0-116 is "installed" and "supported until April 2027" The Kernel is loaded and installed but "not found" Then another window opens and I must choose "Boot from next volume" Then another window where I'm given the choice of booting from 5.15.0-107-generic (on /dev/sda5) This new Kernel is not listed at this window, not sure why not, seems it should be. If I can give you more info. let me know. Ralph Goe Sent with Proton Mail secure email. On Tuesday, July 16th, 2024 at 3:48 PM, Ubuntu Kernel Bot <2068...@bugs.launchpad.net> wrote: > This bug is awaiting verification that the linux-nvidia/5.15.0-1061.62 > kernel in -proposed solves the problem. Please test the kernel and > update this bug with the results. If the problem is solved, change the > tag 'verification-needed-jammy-linux-nvidia' to 'verification-done- > jammy-linux-nvidia'. If the problem still exists, change the tag > 'verification-needed-jammy-linux-nvidia' to 'verification-failed-jammy- > linux-nvidia'. > > > If verification is not done by 5 working days from today, this fix will > be dropped from the source code, and this bug will be closed. > > > See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how > to enable and use -proposed. Thank you! > > > ** Tags added: kernel-spammed-jammy-linux-nvidia-v2 > verification-needed-jammy-linux-nvidia > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (2069485). > https://bugs.launchpad.net/bugs/2068738 > > Title: > AMD GPUs fail with null pointer dereference when IOMMU enabled, > leading to black screen > > Status in linux package in Ubuntu: > Fix Released > Status in linux source package in Jammy: > Fix Released > > Bug description: > BugLink: https://bugs.launchpad.net/bugs/2068738 > > [Impact] > > On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is > enabled, the system fails to boot correctly, and all users see is a > black screen. > > This is caused by a null pointer dereference when enabling the IOMMU > after the device has been initialised. It should happen the other way > around. > > AMD-Vi: AMD IOMMUv2 loaded and initialized > ... > amdgpu: Topology: Add APU node [0x15d8:0x1002] > kfd kfd: amdgpu: added device 1002:15d8 > kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8 > ... > amdgpu :06:00.0: amdgpu: amdgpu_device_ip_init failed > amdgpu :06:00.0: amdgpu: Fatal error during GPU init > amdgpu :06:00.0: amdgpu: amdgpu: finishing device. > ... > BUG: kernel NULL pointer dereference, address: 013c > ... > CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic #122-Ubuntu > ... > RIP: 0010:amdgpu_dm_fini+0x149/0x1f0 [amdgpu] > ... > Call Trace: > > > ? srso_return_thunk+0x5/0x10 > ? show_trace_log_lvl+0x28e/0x2ea > ? show_trace_log_lvl+0x28e/0x2ea > ? dm_hw_fini+0x23/0x30 [amdgpu] > ? show_regs.part.0+0x23/0x29 > ? __die_body.cold+0x8/0xd > ? __die+0x2b/0x37 > ? page_fault_oops+0x13b/0x170 > ? srso_return_thunk+0x5/0x10 > ? do_user_addr_fault+0x321/0x670 > ? srso_return_thunk+0x5/0x10 > ? __free_pages_ok+0x34a/0x4f0 > ? exc_page_fault+0x77/0x170 > ? asm_exc_page_fault+0x27/0x30 > ? amdgpu_dm_fini+0x149/0x1f0 [amdgpu] > dm_hw_fini+0x23/0x30 [amdgpu] > amdgpu_device_ip_fini_early.isra.0+0x278/0x312 [amdgpu] > amdgpu_device_fini_hw+0x156/0x208 [amdgpu] > amdgpu_driver_unload_kms+0x69/0x90 [amdgpu] > amdgpu_driver_load_kms.cold+0x81/0x107 [amdgpu] > amdgpu_pci_probe+0x1d1/0x290 [amdgpu] > local_pci_probe+0x4b/0x90 > ? srso_return_thunk+0x5/0x10 > pci_device_probe+0x119/0x200 > really_probe+0x222/0x420 > __driver_probe_device+0xe8/0x140 > driver_probe_device+0x23/0xc0 > __driver_attach+0xf7/0x1f0 > ? __device_attach_driver+0x140/0x140 > bus_for_each_dev+0x7f/0xd0 > driver_attach+0x1e/0x30 > bus_add_driver+0x148/0x220 > ? srso_return_thunk+0x5/0x10 > driver_register+0x95/0x100 > __pci_register_driver+0x68/0x70 > amdgpu_init+0x7c/0x1000 [amdgpu] > ? 0xc0e0b000 > do_one_initcall+0x49/0x1e0 > ? srso_return_thunk+0x5/0x10 > ? kmem_cache_alloc_trace+0x19e/0x2e0 > do_init_module+0x52/0x260 > load_module+0xb45/0xbe0 > __do_sys_finit_module+0xbf/0x120 > __x64_sys_finit_module+0x18/0x20 > x64_sys_call+0x1ac3/0x1fa0 > do_syscall_64+0x56/0xb0 > ... > entry_SYSCALL_64_after_hwframe+0x67/0xd1 > > A workaround does exist. Users can set "nomodeset" or "amd_iommu=off" > to GRUB_CMDLINE_LINUX_DEFAULT, update-grub and reboot. > > [Fix] > > The regression was caused by the following commit that landed in > 5.15.0-112-generic, and 5.15.150 upstream: > > commit 3c7e53c0d4b43ffe6e7715414b5f2b3177881ecd ubuntu-jammy > Author: Yifan Zhang yifan1.zh...@amd.com > > Date: Tue Sep 28 15:42:35 2021 +0800 > Subject: drm/amdgpu: init iommu after amdkfd device init > Link: >
Re: [Bug 2068738] Re: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen
I don't know if you're getting my response but this fix has not fixed my computer. Unfortunately, I still have the same problem, after updating, I power down and restart, I get: error: file `/boot/' not found. I view the Kernels in the update manager, it shows 5.15.0-116 is "installed" and "supported until April 2027" The Kernel is loaded and installed but "not found" Then another window opens and I must choose "Boot from next volume" Then another window where I'm given the choice of booting from 5.15.0-107-generic (on /dev/sda5) This new Kernel is not listed at this window, not sure why not, seems it should be. If I can give you more info. let me know. Ralph Goe Sent with Proton Mail secure email. On Tuesday, July 16th, 2024 at 3:48 PM, Ubuntu Kernel Bot <2068...@bugs.launchpad.net> wrote: > This bug is awaiting verification that the linux-nvidia/5.15.0-1061.62 > kernel in -proposed solves the problem. Please test the kernel and > update this bug with the results. If the problem is solved, change the > tag 'verification-needed-jammy-linux-nvidia' to 'verification-done- > jammy-linux-nvidia'. If the problem still exists, change the tag > 'verification-needed-jammy-linux-nvidia' to 'verification-failed-jammy- > linux-nvidia'. > > > If verification is not done by 5 working days from today, this fix will > be dropped from the source code, and this bug will be closed. > > > See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how > to enable and use -proposed. Thank you! > > > ** Tags added: kernel-spammed-jammy-linux-nvidia-v2 > verification-needed-jammy-linux-nvidia > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (2069485). > https://bugs.launchpad.net/bugs/2068738 > > Title: > AMD GPUs fail with null pointer dereference when IOMMU enabled, > leading to black screen > > Status in linux package in Ubuntu: > Fix Released > Status in linux source package in Jammy: > Fix Released > > Bug description: > BugLink: https://bugs.launchpad.net/bugs/2068738 > > [Impact] > > On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is > enabled, the system fails to boot correctly, and all users see is a > black screen. > > This is caused by a null pointer dereference when enabling the IOMMU > after the device has been initialised. It should happen the other way > around. > > AMD-Vi: AMD IOMMUv2 loaded and initialized > ... > amdgpu: Topology: Add APU node [0x15d8:0x1002] > kfd kfd: amdgpu: added device 1002:15d8 > kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8 > ... > amdgpu :06:00.0: amdgpu: amdgpu_device_ip_init failed > amdgpu :06:00.0: amdgpu: Fatal error during GPU init > amdgpu :06:00.0: amdgpu: amdgpu: finishing device. > ... > BUG: kernel NULL pointer dereference, address: 013c > ... > CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic #122-Ubuntu > ... > RIP: 0010:amdgpu_dm_fini+0x149/0x1f0 [amdgpu] > ... > Call Trace: > > > ? srso_return_thunk+0x5/0x10 > ? show_trace_log_lvl+0x28e/0x2ea > ? show_trace_log_lvl+0x28e/0x2ea > ? dm_hw_fini+0x23/0x30 [amdgpu] > ? show_regs.part.0+0x23/0x29 > ? __die_body.cold+0x8/0xd > ? __die+0x2b/0x37 > ? page_fault_oops+0x13b/0x170 > ? srso_return_thunk+0x5/0x10 > ? do_user_addr_fault+0x321/0x670 > ? srso_return_thunk+0x5/0x10 > ? __free_pages_ok+0x34a/0x4f0 > ? exc_page_fault+0x77/0x170 > ? asm_exc_page_fault+0x27/0x30 > ? amdgpu_dm_fini+0x149/0x1f0 [amdgpu] > dm_hw_fini+0x23/0x30 [amdgpu] > amdgpu_device_ip_fini_early.isra.0+0x278/0x312 [amdgpu] > amdgpu_device_fini_hw+0x156/0x208 [amdgpu] > amdgpu_driver_unload_kms+0x69/0x90 [amdgpu] > amdgpu_driver_load_kms.cold+0x81/0x107 [amdgpu] > amdgpu_pci_probe+0x1d1/0x290 [amdgpu] > local_pci_probe+0x4b/0x90 > ? srso_return_thunk+0x5/0x10 > pci_device_probe+0x119/0x200 > really_probe+0x222/0x420 > __driver_probe_device+0xe8/0x140 > driver_probe_device+0x23/0xc0 > __driver_attach+0xf7/0x1f0 > ? __device_attach_driver+0x140/0x140 > bus_for_each_dev+0x7f/0xd0 > driver_attach+0x1e/0x30 > bus_add_driver+0x148/0x220 > ? srso_return_thunk+0x5/0x10 > driver_register+0x95/0x100 > __pci_register_driver+0x68/0x70 > amdgpu_init+0x7c/0x1000 [amdgpu] > ? 0xc0e0b000 > do_one_initcall+0x49/0x1e0 > ? srso_return_thunk+0x5/0x10 > ? kmem_cache_alloc_trace+0x19e/0x2e0 > do_init_module+0x52/0x260 > load_module+0xb45/0xbe0 > __do_sys_finit_module+0xbf/0x120 > __x64_sys_finit_module+0x18/0x20 > x64_sys_call+0x1ac3/0x1fa0 > do_syscall_64+0x56/0xb0 > ... > entry_SYSCALL_64_after_hwframe+0x67/0xd1 > > A workaround does exist. Users can set "nomodeset" or "amd_iommu=off" > to GRUB_CMDLINE_LINUX_DEFAULT, update-grub and reboot. > > [Fix] > > The regression was caused by the following commit that landed in > 5.15.0-112-generic, and 5.15.150 upstream: > > commit 3c7e53c0d4b43ffe6e7715414b5f2b3177881ecd ubuntu-jammy > Author: Yifan Zhang yifan1.zh...@amd.com > > Date: Tue Sep 28 15:42:35 2021
[Bug 2068738] verification-failed-jammy-linux-gke
Not sure if I'm replying correctly, this bug fix did not help me. Unfortunately, I still have the same problem, after updating, I power down and restart, I get: error: file `/boot/' not found. I view the Kernels in the update manager, it shows 5.15.0-116 is "installed" and "supported until April 2027" The Kernel is loaded and installed but "not found" Then another window opens and I must choose "Boot from next volume" Then another window where I'm given the choice of booting from 5.15.0-107-generic (on /dev/sda5) This new Kernel is not listed at this window, not sure why not, seems it should be. If I can give you more info. let me know. Ralph Goe Sent with Proton Mail secure email. On Tuesday, July 16th, 2024 at 9:56 AM, Ubuntu Kernel Bot <2068...@bugs.launchpad.net> wrote: > This bug is awaiting verification that the linux-gke/5.15.0-1063.69 > kernel in -proposed solves the problem. Please test the kernel and > update this bug with the results. If the problem is solved, change the > tag 'verification-needed-jammy-linux-gke' to 'verification-done-jammy- > linux-gke'. If the problem still exists, change the tag 'verification- > needed-jammy-linux-gke' to 'verification-failed-jammy-linux-gke'. > > > If verification is not done by 5 working days from today, this fix will > be dropped from the source code, and this bug will be closed. > > > See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how > to enable and use -proposed. Thank you! > > > ** Tags added: kernel-spammed-jammy-linux-gke-v2 > verification-needed-jammy-linux-gke > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (2069485). > https://bugs.launchpad.net/bugs/2068738 > > Title: > AMD GPUs fail with null pointer dereference when IOMMU enabled, > leading to black screen > > Status in linux package in Ubuntu: > Fix Released > Status in linux source package in Jammy: > Fix Released > > Bug description: > BugLink: https://bugs.launchpad.net/bugs/2068738 > > [Impact] > > On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is > enabled, the system fails to boot correctly, and all users see is a > black screen. > > This is caused by a null pointer dereference when enabling the IOMMU > after the device has been initialised. It should happen the other way > around. > > AMD-Vi: AMD IOMMUv2 loaded and initialized > ... > amdgpu: Topology: Add APU node [0x15d8:0x1002] > kfd kfd: amdgpu: added device 1002:15d8 > kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8 > ... > amdgpu :06:00.0: amdgpu: amdgpu_device_ip_init failed > amdgpu :06:00.0: amdgpu: Fatal error during GPU init > amdgpu :06:00.0: amdgpu: amdgpu: finishing device. > ... > BUG: kernel NULL pointer dereference, address: 013c > ... > CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic #122-Ubuntu > ... > RIP: 0010:amdgpu_dm_fini+0x149/0x1f0 [amdgpu] > ... > Call Trace: > > > ? srso_return_thunk+0x5/0x10 > ? show_trace_log_lvl+0x28e/0x2ea > ? show_trace_log_lvl+0x28e/0x2ea > ? dm_hw_fini+0x23/0x30 [amdgpu] > ? show_regs.part.0+0x23/0x29 > ? __die_body.cold+0x8/0xd > ? __die+0x2b/0x37 > ? page_fault_oops+0x13b/0x170 > ? srso_return_thunk+0x5/0x10 > ? do_user_addr_fault+0x321/0x670 > ? srso_return_thunk+0x5/0x10 > ? __free_pages_ok+0x34a/0x4f0 > ? exc_page_fault+0x77/0x170 > ? asm_exc_page_fault+0x27/0x30 > ? amdgpu_dm_fini+0x149/0x1f0 [amdgpu] > dm_hw_fini+0x23/0x30 [amdgpu] > amdgpu_device_ip_fini_early.isra.0+0x278/0x312 [amdgpu] > amdgpu_device_fini_hw+0x156/0x208 [amdgpu] > amdgpu_driver_unload_kms+0x69/0x90 [amdgpu] > amdgpu_driver_load_kms.cold+0x81/0x107 [amdgpu] > amdgpu_pci_probe+0x1d1/0x290 [amdgpu] > local_pci_probe+0x4b/0x90 > ? srso_return_thunk+0x5/0x10 > pci_device_probe+0x119/0x200 > really_probe+0x222/0x420 > __driver_probe_device+0xe8/0x140 > driver_probe_device+0x23/0xc0 > __driver_attach+0xf7/0x1f0 > ? __device_attach_driver+0x140/0x140 > bus_for_each_dev+0x7f/0xd0 > driver_attach+0x1e/0x30 > bus_add_driver+0x148/0x220 > ? srso_return_thunk+0x5/0x10 > driver_register+0x95/0x100 > __pci_register_driver+0x68/0x70 > amdgpu_init+0x7c/0x1000 [amdgpu] > ? 0xc0e0b000 > do_one_initcall+0x49/0x1e0 > ? srso_return_thunk+0x5/0x10 > ? kmem_cache_alloc_trace+0x19e/0x2e0 > do_init_module+0x52/0x260 > load_module+0xb45/0xbe0 > __do_sys_finit_module+0xbf/0x120 > __x64_sys_finit_module+0x18/0x20 > x64_sys_call+0x1ac3/0x1fa0 > do_syscall_64+0x56/0xb0 > ... > entry_SYSCALL_64_after_hwframe+0x67/0xd1 > > A workaround does exist. Users can set "nomodeset" or "amd_iommu=off" > to GRUB_CMDLINE_LINUX_DEFAULT, update-grub and reboot. > > [Fix] > > The regression was caused by the following commit that landed in > 5.15.0-112-generic, and 5.15.150 upstream: > > commit 3c7e53c0d4b43ffe6e7715414b5f2b3177881ecd ubuntu-jammy > Author: Yifan Zhang yifan1.zh...@amd.com > > Date: Tue Sep 28 15:42:35 2021 +0800 > Subject: drm/amdgpu: init iommu
[Bug 2068738] verification-failed-focal-linux-riscv-5.15
Unfortunately, I still have the same problem, after updating, I power down and restart, I get: error: file `/boot/' not found. I view the Kernels in the update manager, it shows 5.15.0-116 is "installed" and "supported until April 2027" The Kernel is loaded and installed but "not found" Then another window opens and I must choose "Boot from next volume" Then another window where I'm given the choice of booting from 5.15.0-107-generic (on /dev/sda5) This new Kernel is not listed at this window, not sure why not, seems it should be. If I can give you more info. let me know. Ralph Goe Sent with Proton Mail secure email. On Tuesday, July 16th, 2024 at 7:13 AM, Ubuntu Kernel Bot <2068...@bugs.launchpad.net> wrote: > This bug is awaiting verification that the linux- > riscv-5.15/5.15.0-1062.66~20.04.1 kernel in -proposed solves the > problem. Please test the kernel and update this bug with the results. If > the problem is solved, change the tag 'verification-needed-focal-linux- > riscv-5.15' to 'verification-done-focal-linux-riscv-5.15'. If the > problem still exists, change the tag 'verification-needed-focal-linux- > riscv-5.15' to 'verification-failed-focal-linux-riscv-5.15'. > > > If verification is not done by 5 working days from today, this fix will > be dropped from the source code, and this bug will be closed. > > > See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how > to enable and use -proposed. Thank you! > > > ** Tags added: kernel-spammed-focal-linux-riscv-5.15-v2 > verification-needed-focal-linux-riscv-5.15 > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (2069485). > https://bugs.launchpad.net/bugs/2068738 > > Title: > AMD GPUs fail with null pointer dereference when IOMMU enabled, > leading to black screen > > Status in linux package in Ubuntu: > Fix Released > Status in linux source package in Jammy: > Fix Released > > Bug description: > BugLink: https://bugs.launchpad.net/bugs/2068738 > > [Impact] > > On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is > enabled, the system fails to boot correctly, and all users see is a > black screen. > > This is caused by a null pointer dereference when enabling the IOMMU > after the device has been initialised. It should happen the other way > around. > > AMD-Vi: AMD IOMMUv2 loaded and initialized > ... > amdgpu: Topology: Add APU node [0x15d8:0x1002] > kfd kfd: amdgpu: added device 1002:15d8 > kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8 > ... > amdgpu :06:00.0: amdgpu: amdgpu_device_ip_init failed > amdgpu :06:00.0: amdgpu: Fatal error during GPU init > amdgpu :06:00.0: amdgpu: amdgpu: finishing device. > ... > BUG: kernel NULL pointer dereference, address: 013c > ... > CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic #122-Ubuntu > ... > RIP: 0010:amdgpu_dm_fini+0x149/0x1f0 [amdgpu] > ... > Call Trace: > > > ? srso_return_thunk+0x5/0x10 > ? show_trace_log_lvl+0x28e/0x2ea > ? show_trace_log_lvl+0x28e/0x2ea > ? dm_hw_fini+0x23/0x30 [amdgpu] > ? show_regs.part.0+0x23/0x29 > ? __die_body.cold+0x8/0xd > ? __die+0x2b/0x37 > ? page_fault_oops+0x13b/0x170 > ? srso_return_thunk+0x5/0x10 > ? do_user_addr_fault+0x321/0x670 > ? srso_return_thunk+0x5/0x10 > ? __free_pages_ok+0x34a/0x4f0 > ? exc_page_fault+0x77/0x170 > ? asm_exc_page_fault+0x27/0x30 > ? amdgpu_dm_fini+0x149/0x1f0 [amdgpu] > dm_hw_fini+0x23/0x30 [amdgpu] > amdgpu_device_ip_fini_early.isra.0+0x278/0x312 [amdgpu] > amdgpu_device_fini_hw+0x156/0x208 [amdgpu] > amdgpu_driver_unload_kms+0x69/0x90 [amdgpu] > amdgpu_driver_load_kms.cold+0x81/0x107 [amdgpu] > amdgpu_pci_probe+0x1d1/0x290 [amdgpu] > local_pci_probe+0x4b/0x90 > ? srso_return_thunk+0x5/0x10 > pci_device_probe+0x119/0x200 > really_probe+0x222/0x420 > __driver_probe_device+0xe8/0x140 > driver_probe_device+0x23/0xc0 > __driver_attach+0xf7/0x1f0 > ? __device_attach_driver+0x140/0x140 > bus_for_each_dev+0x7f/0xd0 > driver_attach+0x1e/0x30 > bus_add_driver+0x148/0x220 > ? srso_return_thunk+0x5/0x10 > driver_register+0x95/0x100 > __pci_register_driver+0x68/0x70 > amdgpu_init+0x7c/0x1000 [amdgpu] > ? 0xc0e0b000 > do_one_initcall+0x49/0x1e0 > ? srso_return_thunk+0x5/0x10 > ? kmem_cache_alloc_trace+0x19e/0x2e0 > do_init_module+0x52/0x260 > load_module+0xb45/0xbe0 > __do_sys_finit_module+0xbf/0x120 > __x64_sys_finit_module+0x18/0x20 > x64_sys_call+0x1ac3/0x1fa0 > do_syscall_64+0x56/0xb0 > ... > entry_SYSCALL_64_after_hwframe+0x67/0xd1 > > A workaround does exist. Users can set "nomodeset" or "amd_iommu=off" > to GRUB_CMDLINE_LINUX_DEFAULT, update-grub and reboot. > > [Fix] > > The regression was caused by the following commit that landed in > 5.15.0-112-generic, and 5.15.150 upstream: > > commit 3c7e53c0d4b43ffe6e7715414b5f2b3177881ecd ubuntu-jammy > Author: Yifan Zhang yifan1.zh...@amd.com > > Date: Tue Sep 28 15:42:35 2021 +0800 > Subject: drm/amdgpu: init iommu after amdkfd device init >
Fw: Re: [Bug 2068738] Re: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen
I've attached a pic of Update Manager showing Kernels installed. Sent with Proton Mail secure email. --- Forwarded Message --- From: Roger Ramjet Date: On Monday, July 15th, 2024 at 8:42 AM Subject: Fw: Re: [Bug 2068738] Re: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen To: Bug 2068738 <2068...@bugs.launchpad.net> > I view the Kernels in the update manager, it shows 5.15.0-116 is "installed" > and "supported until April 2027" > > The Kernel is loaded and installed but "not found" > Then another window opens and I must choose "Boot from next volume" > Then I'm given the choice of booting from 5.15.0-107-generic (on /dev/sda5) > > If I can give you more info. let me know. > > Thanks, Ralph Goe > > > > > Sent with Proton Mail secure email. > > > --- Forwarded Message --- > From: Roger Ramjet eo...@proton.me > > Date: On Monday, July 15th, 2024 at 8:33 AM > Subject: Re: [Bug 2068738] Re: AMD GPUs fail with null pointer dereference > when IOMMU enabled, leading to black screen > To: Bug 2068738 2068...@bugs.launchpad.net > > > > > Unfortunately, I still have the same problem, after updating, I power down > > and restart, I get: > > error: file `/boot/' not found. > > > > Not sure what to do now. > > > > Thanks, Ralph Goe > > > > Sent with Proton Mail secure email. > > > > On Monday, July 15th, 2024 at 4:22 AM, Launchpad Bug Tracker > > 2068...@bugs.launchpad.net wrote: > > > > > This bug was fixed in the package linux - 5.15.0-116.126 > > > > > > --- > > > linux (5.15.0-116.126) jammy; urgency=medium > > > > > > * jammy/linux: 5.15.0-116.126 -proposed tracker (LP: #2071603) > > > > > > * idxd: NULL pointer dereference reading wq op_config attribute (LP: > > > #2069081) > > > - SAUCE: dmaengine: idxd: set is_visible member of idxd_wq_attribute_group > > > > > > * AMD GPUs fail with null pointer dereference when IOMMU enabled, leading > > > to > > > black screen (LP: #2068738) > > > - SAUCE: Revert "drm/amdgpu: init iommu after amdkfd device init" > > > > > > linux (5.15.0-115.125) jammy; urgency=medium > > > > > > * jammy/linux: 5.15.0-115.125 -proposed tracker (LP: #2068396) > > > > > > * Packaging resync (LP: #1786013) > > > - [Packaging] debian.master/dkms-versions -- update from kernel-versions > > > (main/2024.06.10) > > > > > > * Jammy update: v5.15.158 upstream stable release (LP: #2067974) > > > - smb: client: fix rename(2) regression against samba > > > - cifs: reinstate original behavior again for forceuid/forcegid > > > - HID: intel-ish-hid: ipc: Fix dev_err usage with uninitialized dev->devc > > > > > > - HID: logitech-dj: allow mice to use all types of reports > > > - arm64: dts: rockchip: enable internal pull-up on Q7_USB_ID for RK3399 > > > Puma > > > - arm64: dts: rockchip: fix alphabetical ordering RK3399 puma > > > - arm64: dts: rockchip: enable internal pull-up on PCIE_WAKE# for RK3399 > > > Puma > > > - arm64: dts: rockchip: Remove unsupported node from the Pinebook Pro dts > > > - arm64: dts: mediatek: mt8183: Add power-domains properity to mfgcfg > > > - arm64: dts: mediatek: mt7622: add support for coherent DMA > > > - arm64: dts: mediatek: mt7622: introduce nodes for Wireless Ethernet > > > Dispatch > > > - arm64: dts: mediatek: mt7622: fix clock controllers > > > - arm64: dts: mediatek: mt7622: fix IR nodename > > > - arm64: dts: mediatek: mt7622: fix ethernet controller "compatible" > > > - arm64: dts: mediatek: mt7622: drop "reset-names" from thermal block > > > - arm64: dts: mediatek: mt2712: fix validation errors > > > - ARC: [plat-hsdk]: Remove misplaced interrupt-cells property > > > - wifi: iwlwifi: mvm: remove old PASN station when adding a new one > > > - wifi: iwlwifi: mvm: return uid from iwl_mvm_build_scan_cmd > > > - vxlan: drop packets from invalid src-address > > > - mlxsw: core: Unregister EMAD trap using FORWARD action > > > - icmp: prevent possible NULL dereferences from icmp_build_probe() > > > - bridge/br_netlink.c: no need to return void function > > > - NFC: trf7970a: disable all regulators on removal > > > - ipv4: check for NULL idev in ip_route_use_hint() > > > - net: usb: ax88179_178a: stop lying about skb->truesi
Fw: Re: [Bug 2068738] Re: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen
I view the Kernels in the update manager, it shows 5.15.0-116 is "installed" and "supported until April 2027" The Kernel is loaded and installed but "not found" Then another window opens and I must choose "Boot from next volume" Then I'm given the choice of booting from 5.15.0-107-generic (on /dev/sda5) If I can give you more info. let me know. Thanks, Ralph Goe Sent with Proton Mail secure email. --- Forwarded Message --- From: Roger Ramjet Date: On Monday, July 15th, 2024 at 8:33 AM Subject: Re: [Bug 2068738] Re: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen To: Bug 2068738 <2068...@bugs.launchpad.net> > Unfortunately, I still have the same problem, after updating, I power down > and restart, I get: > error: file `/boot/' not found. > > > Not sure what to do now. > > Thanks, Ralph Goe > > > > > Sent with Proton Mail secure email. > > > On Monday, July 15th, 2024 at 4:22 AM, Launchpad Bug Tracker > 2068...@bugs.launchpad.net wrote: > > > This bug was fixed in the package linux - 5.15.0-116.126 > > > > --- > > linux (5.15.0-116.126) jammy; urgency=medium > > > > * jammy/linux: 5.15.0-116.126 -proposed tracker (LP: #2071603) > > > > * idxd: NULL pointer dereference reading wq op_config attribute (LP: > > #2069081) > > - SAUCE: dmaengine: idxd: set is_visible member of idxd_wq_attribute_group > > > > * AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to > > black screen (LP: #2068738) > > - SAUCE: Revert "drm/amdgpu: init iommu after amdkfd device init" > > > > linux (5.15.0-115.125) jammy; urgency=medium > > > > * jammy/linux: 5.15.0-115.125 -proposed tracker (LP: #2068396) > > > > * Packaging resync (LP: #1786013) > > - [Packaging] debian.master/dkms-versions -- update from kernel-versions > > (main/2024.06.10) > > > > * Jammy update: v5.15.158 upstream stable release (LP: #2067974) > > - smb: client: fix rename(2) regression against samba > > - cifs: reinstate original behavior again for forceuid/forcegid > > - HID: intel-ish-hid: ipc: Fix dev_err usage with uninitialized dev->devc > > > > - HID: logitech-dj: allow mice to use all types of reports > > - arm64: dts: rockchip: enable internal pull-up on Q7_USB_ID for RK3399 Puma > > - arm64: dts: rockchip: fix alphabetical ordering RK3399 puma > > - arm64: dts: rockchip: enable internal pull-up on PCIE_WAKE# for RK3399 > > Puma > > - arm64: dts: rockchip: Remove unsupported node from the Pinebook Pro dts > > - arm64: dts: mediatek: mt8183: Add power-domains properity to mfgcfg > > - arm64: dts: mediatek: mt7622: add support for coherent DMA > > - arm64: dts: mediatek: mt7622: introduce nodes for Wireless Ethernet > > Dispatch > > - arm64: dts: mediatek: mt7622: fix clock controllers > > - arm64: dts: mediatek: mt7622: fix IR nodename > > - arm64: dts: mediatek: mt7622: fix ethernet controller "compatible" > > - arm64: dts: mediatek: mt7622: drop "reset-names" from thermal block > > - arm64: dts: mediatek: mt2712: fix validation errors > > - ARC: [plat-hsdk]: Remove misplaced interrupt-cells property > > - wifi: iwlwifi: mvm: remove old PASN station when adding a new one > > - wifi: iwlwifi: mvm: return uid from iwl_mvm_build_scan_cmd > > - vxlan: drop packets from invalid src-address > > - mlxsw: core: Unregister EMAD trap using FORWARD action > > - icmp: prevent possible NULL dereferences from icmp_build_probe() > > - bridge/br_netlink.c: no need to return void function > > - NFC: trf7970a: disable all regulators on removal > > - ipv4: check for NULL idev in ip_route_use_hint() > > - net: usb: ax88179_178a: stop lying about skb->truesize > > > > - net: gtp: Fix Use-After-Free in gtp_dellink > > - ipvs: Fix checksumming on GSO of SCTP packets > > - net: openvswitch: Fix Use-After-Free in ovs_ct_exit > > - mlxsw: spectrum_acl_tcam: Fix race during rehash delayed work > > - mlxsw: spectrum_acl_tcam: Fix possible use-after-free during activity > > update > > - mlxsw: spectrum_acl_tcam: Fix possible use-after-free during rehash > > - mlxsw: spectrum_acl_tcam: Rate limit error message > > - mlxsw: spectrum_acl_tcam: Fix memory leak during rehash > > - mlxsw: spectrum_acl_tcam: Fix warning during rehash > > - mlxsw: spectrum_acl_tcam: Fix incorrect list API usage > > - mlxsw: spectrum_acl_tcam: Fix memory leak when canceling rehash work > > - netfilter: nf_tables: honor table dormant flag from netdev release event
Re: [Bug 2068738] Re: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen
Unfortunately, I still have the same problem, after updating, I power down and
restart, I get:
error: file `/boot/' not found.
Not sure what to do now.
Thanks, Ralph Goe
Sent with Proton Mail secure email.
On Monday, July 15th, 2024 at 4:22 AM, Launchpad Bug Tracker
<2068...@bugs.launchpad.net> wrote:
> This bug was fixed in the package linux - 5.15.0-116.126
>
> ---
> linux (5.15.0-116.126) jammy; urgency=medium
>
> * jammy/linux: 5.15.0-116.126 -proposed tracker (LP: #2071603)
>
> * idxd: NULL pointer dereference reading wq op_config attribute (LP: #2069081)
> - SAUCE: dmaengine: idxd: set is_visible member of idxd_wq_attribute_group
>
> * AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to
> black screen (LP: #2068738)
> - SAUCE: Revert "drm/amdgpu: init iommu after amdkfd device init"
>
> linux (5.15.0-115.125) jammy; urgency=medium
>
> * jammy/linux: 5.15.0-115.125 -proposed tracker (LP: #2068396)
>
> * Packaging resync (LP: #1786013)
> - [Packaging] debian.master/dkms-versions -- update from kernel-versions
> (main/2024.06.10)
>
> * Jammy update: v5.15.158 upstream stable release (LP: #2067974)
> - smb: client: fix rename(2) regression against samba
> - cifs: reinstate original behavior again for forceuid/forcegid
> - HID: intel-ish-hid: ipc: Fix dev_err usage with uninitialized dev->devc
>
> - HID: logitech-dj: allow mice to use all types of reports
> - arm64: dts: rockchip: enable internal pull-up on Q7_USB_ID for RK3399 Puma
> - arm64: dts: rockchip: fix alphabetical ordering RK3399 puma
> - arm64: dts: rockchip: enable internal pull-up on PCIE_WAKE# for RK3399 Puma
> - arm64: dts: rockchip: Remove unsupported node from the Pinebook Pro dts
> - arm64: dts: mediatek: mt8183: Add power-domains properity to mfgcfg
> - arm64: dts: mediatek: mt7622: add support for coherent DMA
> - arm64: dts: mediatek: mt7622: introduce nodes for Wireless Ethernet Dispatch
> - arm64: dts: mediatek: mt7622: fix clock controllers
> - arm64: dts: mediatek: mt7622: fix IR nodename
> - arm64: dts: mediatek: mt7622: fix ethernet controller "compatible"
> - arm64: dts: mediatek: mt7622: drop "reset-names" from thermal block
> - arm64: dts: mediatek: mt2712: fix validation errors
> - ARC: [plat-hsdk]: Remove misplaced interrupt-cells property
> - wifi: iwlwifi: mvm: remove old PASN station when adding a new one
> - wifi: iwlwifi: mvm: return uid from iwl_mvm_build_scan_cmd
> - vxlan: drop packets from invalid src-address
> - mlxsw: core: Unregister EMAD trap using FORWARD action
> - icmp: prevent possible NULL dereferences from icmp_build_probe()
> - bridge/br_netlink.c: no need to return void function
> - NFC: trf7970a: disable all regulators on removal
> - ipv4: check for NULL idev in ip_route_use_hint()
> - net: usb: ax88179_178a: stop lying about skb->truesize
>
> - net: gtp: Fix Use-After-Free in gtp_dellink
> - ipvs: Fix checksumming on GSO of SCTP packets
> - net: openvswitch: Fix Use-After-Free in ovs_ct_exit
> - mlxsw: spectrum_acl_tcam: Fix race during rehash delayed work
> - mlxsw: spectrum_acl_tcam: Fix possible use-after-free during activity update
> - mlxsw: spectrum_acl_tcam: Fix possible use-after-free during rehash
> - mlxsw: spectrum_acl_tcam: Rate limit error message
> - mlxsw: spectrum_acl_tcam: Fix memory leak during rehash
> - mlxsw: spectrum_acl_tcam: Fix warning during rehash
> - mlxsw: spectrum_acl_tcam: Fix incorrect list API usage
> - mlxsw: spectrum_acl_tcam: Fix memory leak when canceling rehash work
> - netfilter: nf_tables: honor table dormant flag from netdev release event
> path
> - i40e: Do not use WQ_MEM_RECLAIM flag for workqueue
> - i40e: Report MFS in decimal base instead of hex
> - iavf: Fix TC config comparison with existing adapter TC config
> - net: ethernet: ti: am65-cpts: Fix PTPv1 message type on TX packets
> - af_unix: Suppress false-positive lockdep splat for spin_lock() in
> __unix_gc().
> - serial: core: Provide port lock wrappers
> - serial: mxs-auart: add spinlock around changing cts state
> - drm-print: add drm_dbg_driver to improve namespace symmetry
> - drm/vmwgfx: Fix crtc's atomic check conditional
> - Revert "crypto: api - Disallow identical driver names"
> - net/mlx5e: Fix a race in command alloc flow
> - tracing: Show size of requested perf buffer
> - tracing: Increase PERF_MAX_TRACE_SIZE to handle Sentinel1 and docker
> together
> - x86/cpu: Fix check for RDPKRU in __show_regs()
> - Bluetooth: Fix type of len in {l2cap,sco}_sock_getsockopt_old()
> - Bluetooth: btusb: Add Realtek RTL8852BE support ID 0x0bda:0x4853
> - Bluetooth: qca: fix NULL-deref on non-serdev suspend
> - mmc: sdhci-msm: pervent access to suspended controller
> - btrfs: fix information leak in btrfs_ioctl_logical_to_ino()
> - cpu: Re-enable CPU mitigations by default for !X86 architectures
> - [Configs] Update CPU mitigation configs
> - arm64: dts: rockchip: enable internal pull-up for Q7_THRM# on RK3399 Puma
> - drm/amdgpu/sdma5.2: use legacy
Re: [Bug 2068738] Re: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen
I just loaded Linux Mint Kernel 5.15.0-113 and it is not recognized at all, I'm told to load a Kernel first, press any key and I have to go back to the index of Linux Kernels and choose 5.15.0-107 to power up. Thanks, Ralph Sent with Proton Mail secure email. On Tuesday, June 18th, 2024 at 7:12 AM, Roger Ramjet wrote: > Thank you Matthew. > > > > > Sent with Proton Mail secure email. > > > On Tuesday, June 18th, 2024 at 2:41 AM, Matthew Ruffell > 2068...@bugs.launchpad.net wrote: > > > Hi everyone, > > > > I spoke with Stefan Bader of the Kernel Team again. They are planning to > > include > > the patch in a respin of the current 2024.06.10 SRU cycle. > > https://kernel.ubuntu.com/ > > > > I will let you know once the kernel has been built and placed into > > -proposed for > > verification. > > > > But at this stage, as long as the respin occurs, this should be released the > > week of 8th July, give or take a few days, if anything else pops up. > > > > Thanks, > > Matthew > > > > -- > > You received this bug notification because you are subscribed to a > > duplicate bug report (2069485). > > https://bugs.launchpad.net/bugs/2068738 > > > > Title: > > AMD GPUs fail with null pointer dereference when IOMMU enabled, > > leading to black screen > > > > Status in linux package in Ubuntu: > > Fix Released > > Status in linux source package in Jammy: > > Fix Committed > > > > Bug description: > > BugLink: https://bugs.launchpad.net/bugs/2068738 > > > > [Impact] > > > > On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is > > enabled, the system fails to boot correctly, and all users see is a > > black screen. > > > > This is caused by a null pointer dereference when enabling the IOMMU > > after the device has been initialised. It should happen the other way > > around. > > > > AMD-Vi: AMD IOMMUv2 loaded and initialized > > ... > > amdgpu: Topology: Add APU node [0x15d8:0x1002] > > kfd kfd: amdgpu: added device 1002:15d8 > > kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8 > > ... > > amdgpu :06:00.0: amdgpu: amdgpu_device_ip_init failed > > amdgpu :06:00.0: amdgpu: Fatal error during GPU init > > amdgpu :06:00.0: amdgpu: amdgpu: finishing device. > > ... > > BUG: kernel NULL pointer dereference, address: 013c > > ... > > CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic > > #122-Ubuntu > > ... > > RIP: 0010:amdgpu_dm_fini+0x149/0x1f0 [amdgpu] > > ... > > Call Trace: > > > > > > ? srso_return_thunk+0x5/0x10 > > ? show_trace_log_lvl+0x28e/0x2ea > > ? show_trace_log_lvl+0x28e/0x2ea > > ? dm_hw_fini+0x23/0x30 [amdgpu] > > ? show_regs.part.0+0x23/0x29 > > ? __die_body.cold+0x8/0xd > > ? __die+0x2b/0x37 > > ? page_fault_oops+0x13b/0x170 > > ? srso_return_thunk+0x5/0x10 > > ? do_user_addr_fault+0x321/0x670 > > ? srso_return_thunk+0x5/0x10 > > ? __free_pages_ok+0x34a/0x4f0 > > ? exc_page_fault+0x77/0x170 > > ? asm_exc_page_fault+0x27/0x30 > > ? amdgpu_dm_fini+0x149/0x1f0 [amdgpu] > > dm_hw_fini+0x23/0x30 [amdgpu] > > amdgpu_device_ip_fini_early.isra.0+0x278/0x312 [amdgpu] > > amdgpu_device_fini_hw+0x156/0x208 [amdgpu] > > amdgpu_driver_unload_kms+0x69/0x90 [amdgpu] > > amdgpu_driver_load_kms.cold+0x81/0x107 [amdgpu] > > amdgpu_pci_probe+0x1d1/0x290 [amdgpu] > > local_pci_probe+0x4b/0x90 > > ? srso_return_thunk+0x5/0x10 > > pci_device_probe+0x119/0x200 > > really_probe+0x222/0x420 > > __driver_probe_device+0xe8/0x140 > > driver_probe_device+0x23/0xc0 > > __driver_attach+0xf7/0x1f0 > > ? __device_attach_driver+0x140/0x140 > > bus_for_each_dev+0x7f/0xd0 > > driver_attach+0x1e/0x30 > > bus_add_driver+0x148/0x220 > > ? srso_return_thunk+0x5/0x10 > > driver_register+0x95/0x100 > > __pci_register_driver+0x68/0x70 > > amdgpu_init+0x7c/0x1000 [amdgpu] > > ? 0xc0e0b000 > > do_one_initcall+0x49/0x1e0 > > ? srso_return_thunk+0x5/0x10 > > ? kmem_cache_alloc_trace+0x19e/0x2e0 > > do_init_module+0x52/0x260 > > load_module+0xb45/0xbe0 > > __do_sys_finit_module+0xbf/0x120 > > __x64_sys_finit_module+0x18/0x20 > > x64_sys_call+0x1ac3/0x1fa0 > > do_syscall_64+0x56/0xb0 > > ... > > entry_SYSCALL_64_after_hwframe+0x67/0xd1 > > > > A workaround does exist. Users can set "nomodeset" or "amd_iommu=off&qu
Re: [Bug 2068738] Re: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen
Thank you Matthew. Sent with Proton Mail secure email. On Tuesday, June 18th, 2024 at 2:41 AM, Matthew Ruffell <2068...@bugs.launchpad.net> wrote: > Hi everyone, > > I spoke with Stefan Bader of the Kernel Team again. They are planning to > include > the patch in a respin of the current 2024.06.10 SRU cycle. > https://kernel.ubuntu.com/ > > I will let you know once the kernel has been built and placed into -proposed > for > verification. > > But at this stage, as long as the respin occurs, this should be released the > week of 8th July, give or take a few days, if anything else pops up. > > Thanks, > Matthew > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (2069485). > https://bugs.launchpad.net/bugs/2068738 > > Title: > AMD GPUs fail with null pointer dereference when IOMMU enabled, > leading to black screen > > Status in linux package in Ubuntu: > Fix Released > Status in linux source package in Jammy: > Fix Committed > > Bug description: > BugLink: https://bugs.launchpad.net/bugs/2068738 > > [Impact] > > On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is > enabled, the system fails to boot correctly, and all users see is a > black screen. > > This is caused by a null pointer dereference when enabling the IOMMU > after the device has been initialised. It should happen the other way > around. > > AMD-Vi: AMD IOMMUv2 loaded and initialized > ... > amdgpu: Topology: Add APU node [0x15d8:0x1002] > kfd kfd: amdgpu: added device 1002:15d8 > kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8 > ... > amdgpu :06:00.0: amdgpu: amdgpu_device_ip_init failed > amdgpu :06:00.0: amdgpu: Fatal error during GPU init > amdgpu :06:00.0: amdgpu: amdgpu: finishing device. > ... > BUG: kernel NULL pointer dereference, address: 013c > ... > CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic #122-Ubuntu > ... > RIP: 0010:amdgpu_dm_fini+0x149/0x1f0 [amdgpu] > ... > Call Trace: > > > ? srso_return_thunk+0x5/0x10 > ? show_trace_log_lvl+0x28e/0x2ea > ? show_trace_log_lvl+0x28e/0x2ea > ? dm_hw_fini+0x23/0x30 [amdgpu] > ? show_regs.part.0+0x23/0x29 > ? __die_body.cold+0x8/0xd > ? __die+0x2b/0x37 > ? page_fault_oops+0x13b/0x170 > ? srso_return_thunk+0x5/0x10 > ? do_user_addr_fault+0x321/0x670 > ? srso_return_thunk+0x5/0x10 > ? __free_pages_ok+0x34a/0x4f0 > ? exc_page_fault+0x77/0x170 > ? asm_exc_page_fault+0x27/0x30 > ? amdgpu_dm_fini+0x149/0x1f0 [amdgpu] > dm_hw_fini+0x23/0x30 [amdgpu] > amdgpu_device_ip_fini_early.isra.0+0x278/0x312 [amdgpu] > amdgpu_device_fini_hw+0x156/0x208 [amdgpu] > amdgpu_driver_unload_kms+0x69/0x90 [amdgpu] > amdgpu_driver_load_kms.cold+0x81/0x107 [amdgpu] > amdgpu_pci_probe+0x1d1/0x290 [amdgpu] > local_pci_probe+0x4b/0x90 > ? srso_return_thunk+0x5/0x10 > pci_device_probe+0x119/0x200 > really_probe+0x222/0x420 > __driver_probe_device+0xe8/0x140 > driver_probe_device+0x23/0xc0 > __driver_attach+0xf7/0x1f0 > ? __device_attach_driver+0x140/0x140 > bus_for_each_dev+0x7f/0xd0 > driver_attach+0x1e/0x30 > bus_add_driver+0x148/0x220 > ? srso_return_thunk+0x5/0x10 > driver_register+0x95/0x100 > __pci_register_driver+0x68/0x70 > amdgpu_init+0x7c/0x1000 [amdgpu] > ? 0xc0e0b000 > do_one_initcall+0x49/0x1e0 > ? srso_return_thunk+0x5/0x10 > ? kmem_cache_alloc_trace+0x19e/0x2e0 > do_init_module+0x52/0x260 > load_module+0xb45/0xbe0 > __do_sys_finit_module+0xbf/0x120 > __x64_sys_finit_module+0x18/0x20 > x64_sys_call+0x1ac3/0x1fa0 > do_syscall_64+0x56/0xb0 > ... > entry_SYSCALL_64_after_hwframe+0x67/0xd1 > > A workaround does exist. Users can set "nomodeset" or "amd_iommu=off" > to GRUB_CMDLINE_LINUX_DEFAULT, update-grub and reboot. > > [Fix] > > The regression was caused by the following commit that landed in > 5.15.0-112-generic, and 5.15.150 upstream: > > commit 3c7e53c0d4b43ffe6e7715414b5f2b3177881ecd ubuntu-jammy > Author: Yifan Zhang yifan1.zh...@amd.com > > Date: Tue Sep 28 15:42:35 2021 +0800 > Subject: drm/amdgpu: init iommu after amdkfd device init > Link: > https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?id=3c7e53c0d4b43ffe6e7715414b5f2b3177881ecd > > The fix is to revert this patch, as it was not suppose to be > backported to 5.15 stable. > > The mailing list discussion with AMD developers is: > > https://lore.kernel.org/amd-gfx/20240523173031.4212-1-w_ar...@gmx.de/ > > The fix hasn't been acknowledged by Greg KH or Sasha Levin yet, so > sending as a Ubuntu SAUCE patch. If the upstream status changes, we > can NAK and resend. > > [Testcase] > > You need a system with an AMD Picasso/Raven 2 device. It will likely > be an APU, and not a discrete graphics card, but any AMD Picasso/Raven > 2 device is affected. > > Install the kernel and boot. Make sure full modesetting is enabled. > > There is a test kernel available in the ppa below: > > https://launchpad.net/~mruffell/+archive/ubuntu/lp2068738-test > > If you install the
Re: [Bug 2069485] Re: won't boot on linux kernal 5.15.0-112
: Mass Storage driver: usb-storage interfaces: 1 rev: 1.1 speed: 12 Mb/s power: 100mA chip-ID: 054c:019e class-ID: 0806 serial: Device-2: 1-3.4:6 info: Integrated Express UDisk type: Mass Storage driver: usb-storage interfaces: 1 rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 048d:04d2 class-ID: 0806 serial: Device-3: 1-4:4 info: Cheng Uei Precision Industry (Foxlink) HP TrueVision HD Camera type: Video driver: uvcvideo interfaces: 2 rev: 2.0 speed: 480 Mb/s power: 500mA chip-ID: 05c8:03d2 class-ID: 0e02 Hub-3: 2-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003 class-ID: 0900 Hub-4: 3-0:1 info: Hi-speed hub with single TT ports: 2 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900 Device-1: 3-1:2 info: Realtek Bluetooth 4.2 Adapter type: Bluetooth driver: btusb interfaces: 2 rev: 1.1 speed: 12 Mb/s power: 500mA chip-ID: 0bda:b00a class-ID: e001 serial: Hub-5: 4-0:1 info: Super-speed hub ports: 1 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003 class-ID: 0900 Sensors: System Temperatures: cpu: 58.0 C mobo: 0.0 C gpu: amdgpu temp: 57.0 C Fan Speeds (RPM): N/A Repos: Packages: 2582 apt: 2567 flatpak: 15 No active apt repos in: /etc/apt/sources.list Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 1: deb http: //packages.linuxmint.com virginia main upstream import backport 2: deb http: //archive.ubuntu.com/ubuntu jammy main restricted universe multiverse 3: deb http: //archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse 4: deb http: //archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse 5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse Info: Processes: 293 Uptime: 1d 8h 16m wakeups: 55 Memory: 13.56 GiB used: 3.33 GiB (24.6%) Init: systemd v: 249 runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12 Client: Cinnamon v: 6.0.4 inxi: 3.3.13 Sent with Proton Mail secure email. On Sunday, June 16th, 2024 at 6:04 AM, Roger Ramjet wrote: > AMD Ryzen 3 3300U with Radeon Vega Mobile Gtx X 4 > > > > > Sent with Proton Mail secure email. > > > On Sunday, June 16th, 2024 at 3:54 AM, Matthew Ruffell > 2069...@bugs.launchpad.net wrote: > > > Hi Roger, > > > > Does your HP laptop have an AMD APU? AMD GPU? > > > > You are probably suffering from: > > > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2068738 > > > > Thanks, > > Matthew > > > > -- > > You received this bug notification because you are subscribed to the bug > > report. > > https://bugs.launchpad.net/bugs/2069485 > > > > Title: > > won't boot on linux kernal 5.15.0-112 > > > > Status in linux package in Ubuntu: > > New > > > > Bug description: > > Would not boot after updating from Linux 5.15.0-107 to 5.15.0-112, only > > have blank screen, need to shut off by holding the power key down on my HP > > laptop, then going into "Advanced Options for Linux Mint 21.3" and choosing > > 5.15.0-107 line. I have 3 operating systems on my laptop, Linux Ubuntu, > > Mint and windows, everytime I boot, I have to pick Mint. > > Thanks. > > > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069485/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069485 Title: won't boot on linux kernal 5.15.0-112 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2069485] Re: won't boot on linux kernal 5.15.0-112
AMD Ryzen 3 3300U with Radeon Vega Mobile Gtx X 4 Sent with Proton Mail secure email. On Sunday, June 16th, 2024 at 3:54 AM, Matthew Ruffell <2069...@bugs.launchpad.net> wrote: > Hi Roger, > > Does your HP laptop have an AMD APU? AMD GPU? > > You are probably suffering from: > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2068738 > > Thanks, > Matthew > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2069485 > > Title: > won't boot on linux kernal 5.15.0-112 > > Status in linux package in Ubuntu: > New > > Bug description: > Would not boot after updating from Linux 5.15.0-107 to 5.15.0-112, only have > blank screen, need to shut off by holding the power key down on my HP laptop, > then going into "Advanced Options for Linux Mint 21.3" and choosing > 5.15.0-107 line. I have 3 operating systems on my laptop, Linux Ubuntu, Mint > and windows, everytime I boot, I have to pick Mint. > Thanks. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069485/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069485 Title: won't boot on linux kernal 5.15.0-112 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069485] [NEW] won't boot on linux kernal 5.15.0-112
Public bug reported: Would not boot after updating from Linux 5.15.0-107 to 5.15.0-112, only have blank screen, need to shut off by holding the power key down on my HP laptop, then going into "Advanced Options for Linux Mint 21.3" and choosing 5.15.0-107 line. I have 3 operating systems on my laptop, Linux Ubuntu, Mint and windows, everytime I boot, I have to pick Mint. Thanks. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069485 Title: won't boot on linux kernal 5.15.0-112 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063234] [NEW] rsibreak reports once per second kf5idletime_wayland: This plugin does not support polling idle time
Public bug reported: rsibreak is generating this message which ends up in the journal *very second* kf5idletime_wayland: This plugin does not support polling idle time $ journalctl | grep rsibreak | head Mar 22 06:21:21 clamps rsibreak[5422]: kf5idletime_wayland: This plugin does not support polling idle time Mar 22 06:21:22 clamps rsibreak[5422]: kf5idletime_wayland: This plugin does not support polling idle time Mar 22 06:21:23 clamps rsibreak[5422]: kf5idletime_wayland: This plugin does not support polling idle time Mar 22 06:21:24 clamps rsibreak[5422]: kf5idletime_wayland: This plugin does not support polling idle time Mar 22 06:21:25 clamps rsibreak[5422]: kf5idletime_wayland: This plugin does not support polling idle time Mar 22 06:21:26 clamps rsibreak[5422]: kf5idletime_wayland: This plugin does not support polling idle time Mar 22 06:21:27 clamps rsibreak[5422]: kf5idletime_wayland: This plugin does not support polling idle time Mar 22 06:21:28 clamps rsibreak[5422]: kf5idletime_wayland: This plugin does not support polling idle time Mar 22 06:21:29 clamps rsibreak[5422]: kf5idletime_wayland: This plugin does not support polling idle time Mar 22 06:21:30 clamps rsibreak[5422]: kf5idletime_wayland: This plugin does not support polling idle time $ journalctl `type -p rsibreak` | grep "This plugin" | wc -l 858265 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: rsibreak 4:0.12.15-1build2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Apr 23 11:07:11 2024 InstallationDate: Installed on 2020-02-15 (1529 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: rsibreak UpgradeStatus: Upgraded to noble on 2024-04-11 (12 days ago) ** Affects: rsibreak (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063234 Title: rsibreak reports once per second kf5idletime_wayland: This plugin does not support polling idle time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsibreak/+bug/2063234/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868704] Re: Secondary monitor black after rotation
Ah, yes, sorry I forgot there was difference with the flavours. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868704 Title: Secondary monitor black after rotation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1868704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868704] Re: Secondary monitor black after rotation
I'm no longer on 20.04 so can't confirm whether it is still present there (it's still a supported release, right?). It must have been fixed in the interim because it no longer affects me on 23.10. I guess since nobody else seems to have been affected then this can be closed as fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868704 Title: Secondary monitor black after rotation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1868704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797113] Re: Lots of errors from unity-panel-service about gtk_menu_detach flooding syslog
May 19 23:37:18 roger-desktop gnome-panel[2218]: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed May 19 23:37:18 roger-desktop gnome-panel[2218]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 19 23:37:52 roger-desktop rtkit-daemon[1668]: Supervising 7 threads of 4 processes of 1 users. May 19 23:38:02 roger-desktop kernel: [25433.653001] perf: interrupt took too long (3154 > 3152), lowering kernel.perf_event_max_sample_rate to 63250 May 19 23:37:52 roger-desktop rtkit-daemon[1668]: Supervising 7 threads of 4 processes of 1 users. May 19 23:38:18 roger-desktop gnome-panel[2218]: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed May 19 23:38:18 roger-desktop gnome-panel[2218]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 19 23:38:18 roger-desktop gnome-panel[2218]: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed May 19 23:38:18 roger-desktop gnome-panel[2218]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 19 23:38:18 roger-desktop gnome-panel[2218]: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed May 19 23:38:18 roger-desktop gnome-panel[2218]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 19 23:38:48 roger-desktop gnome-panel[2218]: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed May 19 23:38:48 roger-desktop gnome-panel[2218]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 19 23:38:48 roger-desktop gnome-panel[2218]: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed May 19 23:38:48 roger-desktop gnome-panel[2218]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 19 23:38:48 roger-desktop gnome-panel[2218]: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed May 19 23:38:48 roger-desktop gnome-panel[2218]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 19 23:39:28 roger-desktop rtkit-daemon[1668]: Supervising 7 threads of 4 processes of 1 users. May 19 23:39:28 roger-desktop rtkit-daemon[1668]: Supervising 7 threads of 4 processes of 1 users. May 19 23:39:48 roger-desktop gnome-panel[2218]: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed May 19 23:39:48 roger-desktop gnome-panel[2218]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 19 23:39:48 roger-desktop gnome-panel[2218]: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed May 19 23:39:48 roger-desktop gnome-panel[2218]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 19 23:39:48 roger-desktop gnome-panel[2218]: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed May 19 23:39:48 roger-desktop gnome-panel[2218]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 19 23:40:18 roger-desktop gnome-panel[2218]: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed May 19 23:40:18 roger-desktop gnome-panel[2218]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 19 23:40:18 roger-desktop gnome-panel[2218]: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed May 19 23:40:18 roger-desktop gnome-panel[2218]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 19 23:40:18 roger-desktop gnome-panel[2218]: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed May 19 23:40:18 roger-desktop gnome-panel[2218]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 19 23:40:48 roger-desktop gnome-panel[2218]: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed May 19 23:40:48 roger-desktop gnome-panel[2218]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 19 23:40:48 roger-desktop gnome-panel[2218]: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed May 19 23:40:48 roger-desktop gnome-panel[2218]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 19 23:40:48 roger-desktop gnome-panel[2218]: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed May 19 23:40:48 roger-desktop gnome-panel[2218]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 19 23:41:18 roger-desktop gnome-panel[2218]: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797113 Title: Lots of errors from unity-panel-service about gtk_menu_detach flooding syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1797113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972667] [NEW] Permissions problem on run scripts after networkd-dispatcher (1.7-0ubuntu3.4)
Public bug reported: I'm unsure if this is a bug or intended behavior. I posted to answers.launchpad.net but received no helpful replies. On ubuntu 20.04.4 LTS after install of update “networkd-dispatcher (1.7-0ubuntu3.4)”, scripts in /etc/networkd-dispatcher/routable.d with 700 permissions that used to run as expected, fail to do so. E.g., I have some routing commands in /etc/networkd- dispatcher/routable.d/50-iptables that should execute at boot time but stopped after this update installed, and ‘service networkd-dispatcher status’ returns: May 07 14:14:49 Krieger networkd-dispatcher[581]: ERROR:invalid permissions on /etc/networkd-dispatcher/routable.d/50-iptables. Expected mode=0o755, uid=0, gid=0; got mode=0o700, uid=0, > Changing permissions on 50-iptables from 0700 to 0755 corrected the problem. I've read the Changelog for the update, and the later update “networkd- dispatcher (1.7-0ubuntu3.5)” which corrected a regression has also been applied but the unexpected behavior remains. Is this less-restrictive permissions requirement an intended result of the update? Is the perms requirement documented anywhere? I don't see it in the networkd-dispatcher man page. Thank you ** Affects: networkd-dispatcher (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972667 Title: Permissions problem on run scripts after networkd-dispatcher (1.7-0ubuntu3.4) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/networkd-dispatcher/+bug/1972667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960339] [NEW] Problems setting Monday as first day of week
Public bug reported: I came across an interesting issue on my Ubuntu 21.10 machine. Originally I wanted to make the calendar applet in the shell menu to start the week on monday so I set up my language section according to the attached picture. Then I logged out from Gnome and nothing had changed when I logged back in. Pursuing this issue a bit further I thought of using gnome-calendar to isolate the problem but when I started the program from the application launcher, I noticed that gnome-calendar also had sunday as first day of the week. Digging a little deeper among the tips found through Google, I came across a post suggesting to set up my locale to deal with this situation: > locale LANG=sv_SE.UTF-8 LANGUAGE=en LC_CTYPE=sv_SE.UTF-8 LC_NUMERIC=sv_SE.UTF-8 LC_TIME=sv_SE.UTF-8 LC_COLLATE=sv_SE.UTF-8 LC_MONETARY=sv_SE.UTF-8 LC_MESSAGES=en_US.UTF-8 LC_PAPER=sv_SE.UTF-8 LC_NAME=sv_SE.UTF-8 LC_ADDRESS=sv_SE.UTF-8 LC_TELEPHONE=sv_SE.UTF-8 LC_MEASUREMENT=sv_SE.UTF-8 LC_IDENTIFICATION=sv_SE.UTF-8 LC_ALL= > grep first_weekday /usr/share/i18n/locales/sv_SE first_weekday 2 So, I tried starting gnome-calendar from my gnome-terminal, where I knew the regional settings were correct, and I still got the issue with sunday being the first day of the week. For no real reason I restarted the application just to make sure I hadn't committed a user error but the problem still persisted. Being a bit frustrated at the point I rage- quit the program and just as I did that I realised I had to check an appointment so I quickly started gnome-calendar from the same terminal again and got an error message GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying When I re-tried starting gnome-calendar from the same terminal again, the application launched and this time with monday as first day of the week. Steps to reproduce 1. Start gnome-terminal 2. In terminal, issue command gnome-calendar 3. Quit Calendar and issue command gnome-calendar again in the same terminal two more times until error message appears as described above 4. Issue command gnome-calendar 5. Observe start of week is monday (as expected) This problem only seems to occur when I start the X11 session. I logged into the Wayland session to look at another problem and noticed that the calendar applet in the shell had monday as first day of the week. Starting gnome-calendar (from the shell menu) also presented me with a calendar where monday was the first day of the week. Logging out and into the X11 session again made the problem, as originally described above, re-appear. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-calendar 41.0-1 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Tue Feb 8 17:01:43 2022 InstallationDate: Installed on 2021-10-20 (111 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug gnome-calendar impish ** Attachment added: "Language settings" https://bugs.launchpad.net/bugs/1960339/+attachment/5559743/+files/Screenshot%20from%202021-12-10%2018-04-17.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960339 Title: Problems setting Monday as first day of week To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1960339/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908429] Re: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal conn
For info. The bug also means that the systemd journal is growing at an extremely fast rate. Double whammy. All these files by default reside in the root file system. Which is usually created quite small. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908429 Title: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. The offending callback was SourceFunc(). To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1908429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943450] Re: Contacts: Retrieve user S/MIME certificate does not work
Thank you Brian! I verified according to the test plan I made within the description of this bug report and can confirm the hirsute-proposed and focal-proposed packages do fix the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943450 Title: Contacts: Retrieve user S/MIME certificate does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-ews/+bug/1943450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 677139] Hello, 677139
https://bit.ly/31wE2Ox -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/677139 Title: [Realtek ID 275] Recording problem intenal micphone , internal laptop speacker no not work., however when you use speacker or micphone via jacks external audio works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/677139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945842] Re: Newer kernel still has no display w/ KMS enabled
*** This bug is a duplicate of bug 1944397 *** https://bugs.launchpad.net/bugs/1944397 Daniel, I am not sure this is the same bug. I am getting this in Hirsute after a recent kernel update. The warnings appear to be in a different area than those in #1944397 3437:Sep 29 15:33:29 brubeck kernel: [ 16.098988] WARNING: CPU: 3 PID: 65 at drivers/gpu/drm/vc4/vc4_hdmi_regs.h:445 vc4_hdmi_encoder_post_crtc_disable+0x424/0x49c [vc4] 3488:Sep 29 15:33:29 brubeck kernel: [ 16.100017] WARNING: CPU: 3 PID: 65 at drivers/gpu/drm/vc4/vc4_hdmi_regs.h:417 vc4_hdmi_read+0xd8/0x140 [vc4] 3550:Sep 29 15:33:29 brubeck kernel: [ 16.100691] WARNING: CPU: 3 PID: 65 at drivers/gpu/drm/vc4/vc4_hdmi_regs.h:445 vc4_hdmi_encoder_post_crtc_powerdown+0x178/0x1c0 [vc4] 3602:Sep 29 15:33:29 brubeck kernel: [ 16.101324] WARNING: CPU: 3 PID: 65 at drivers/gpu/drm/vc4/vc4_hdmi_regs.h:445 vc5_hdmi_phy_disable+0x198/0x220 [vc4] 3657:Sep 29 15:33:29 brubeck kernel: [ 16.101969] WARNING: CPU: 3 PID: 65 at drivers/gpu/drm/vc4/vc4_hdmi_regs.h:445 vc5_hdmi_phy_disable+0x190/0x220 [vc4] 4621:Sep 29 15:33:37 brubeck kernel: [ 25.770372] WARNING: CPU: 1 PID: 1021 at drivers/gpu/drm/vc4/vc4_hdmi_regs.h:417 vc4_hdmi_read+0xd8/0x140 [vc4] 4836:Sep 29 15:33:40 brubeck kernel: [ 28.247538] WARNING: CPU: 3 PID: at drivers/gpu/drm/vc4/vc4_hdmi_regs.h:417 vc4_hdmi_read+0xd8/0x140 [vc4] 5122:Sep 29 15:33:44 brubeck kernel: [ 31.914079] WARNING: CPU: 2 PID: at drivers/gpu/drm/vc4/vc4_hdmi_regs.h:417 vc4_hdmi_read+0xd8/0x140 [vc4] 5162:Sep 29 15:33:44 brubeck kernel: [ 32.528456] WARNING: CPU: 0 PID: at drivers/gpu/drm/vc4/vc4_hdmi_regs.h:417 vc4_hdmi_read+0xd8/0x140 [vc4] ~ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945842 Title: Newer kernel still has no display w/ KMS enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1945842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945842] Re: Newer kernel still has no display w/ KMS enabled
I am also seeing this after an automatic update from linux- image-5.11.0-1017-raspi to linux-image-5.11.0-1019-raspi. The display output is lost very early on in the boot process. The only way I could get round it was to roll the kernel back to 5.11.0-2017. Roger -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945842 Title: Newer kernel still has no display w/ KMS enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1945842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943450] Re: Contacts: Retrieve user S/MIME certificate does not work
Jeremy, I just verified on Ubuntu 21-04 with the attached patch. ** Attachment added: "evolution-ews_3.40.0-1_3.40.0-1.1.diff.gz" https://bugs.launchpad.net/ubuntu/+source/evolution-ews/+bug/1943450/+attachment/5530398/+files/evolution-ews_3.40.0-1_3.40.0-1.1.diff.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943450 Title: Contacts: Retrieve user S/MIME certificate does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-ews/+bug/1943450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943450] Re: Contacts: Retrieve user S/MIME certificate does not work
Thanks Jeremy! Yes, I will prepare a debdiff for Ubuntu 21.04 as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943450 Title: Contacts: Retrieve user S/MIME certificate does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-ews/+bug/1943450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943450] Re: Contacts: Retrieve user S/MIME certificate does not work
Jeremy, I just updated the bug report with the details and attached a debdiff. ** Attachment added: "debdiff evolution-ews_3.36.5-0ubuntu1.dsc evolution-ews_3.36.5-0ubuntu1.1.dsc" https://bugs.launchpad.net/ubuntu/focal/+source/evolution-ews/+bug/1943450/+attachment/5530281/+files/evolution-ews_3.36.5-0ubuntu1_3.36.5-0ubuntu1.1.diff.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943450 Title: Contacts: Retrieve user S/MIME certificate does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-ews/+bug/1943450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943450] Re: Contacts: Retrieve user S/MIME certificate does not work
** Description changed: - It's currently not possible to retrieve encryption certificates from GAL - when connecting to o365. + [Impact] + * It's currently not possible to retrieve encryption certificates +from Global Address List(GAL) when connecting to e.g., Office365 + + * A manual import of encryption certificates is required to send +encrypted emails. + + * The upstream bug has been fixed upstream and release for impish. + + [Test Plan] + + * Configure an EWS account, e.g., using Office365 + + * Search the Global Address List(GAL) and select a person that has +an encryption certificate stored within the GAL. +There is no certificate visible within Certificates tab. +To send encrypted mails to that Person, the encryption certificate +has to be manually imported via Preferences->Certificates->Contact Certificates. + + * With this bug fix the encryption certificate stored within the GAL will +be visible within the contact details view and encrypted mails can be sent +without manual import of encryption certificates. + + [Where problems could occur] + + * The patch has been tested over two weeks during daily work using + evolution-ews. + + [Other Info] upstream: - - issue: https://gitlab.gnome.org/GNOME/evolution-ews/-/issues/3 - - patch: https://gitlab.gnome.org/GNOME/evolution-ews/uploads/ffa7d7a4934cd6bd8b0f44d8c5a47f8f/ews.patch - The patch has not yet been merged upstream due to hard code freeze. - - I've back-ported the patch to evolution-ews 3.36.5 so it could be - shipped with Ubuntu LTS. Would be great if you could integrate that and - ship it with Ubuntu LTS, so people could benefit already today. + * issue: https://gitlab.gnome.org/GNOME/evolution-ews/-/issues/3 + * upstream fix is merged and will be available with 3.43.1+ and 3.42.1+. + * https://gitlab.gnome.org/GNOME/evolution-ews/-/commit/1284316bcc442f66c68aa65c226b5c9e3e774ec4 + * https://gitlab.gnome.org/GNOME/evolution-ews/-/commit/9ea6bc01136e420078c2a0f4140108e79cf8d538 + * back-porte to evolution-ews 3.36.5 https://bugs.launchpad.net/ubuntu/focal/+source/evolution-ews/+bug/1943450/+attachment/5524954/+files/0001-Contacts-Retrieve-user-S-MIME-certificate.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943450 Title: Contacts: Retrieve user S/MIME certificate does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-ews/+bug/1943450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943450] Re: Contacts: Retrieve user S/MIME certificate does not work
upstream fix is merged and will be available with 3.43.1+ and 3.42.1+. - https://gitlab.gnome.org/GNOME/evolution-ews/-/commit/1284316bcc442f66c68aa65c226b5c9e3e774ec4 - https://gitlab.gnome.org/GNOME/evolution-ews/-/commit/9ea6bc01136e420078c2a0f4140108e79cf8d538 would be great to get the backport I made into Ubuntu LTS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943450 Title: Contacts: Retrieve user S/MIME certificate does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-ews/+bug/1943450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943450] [NEW] Contacts: Retrieve user S/MIME certificate does not work
Public bug reported: It's currently not possible to retrieve encryption certificates from GAL when connecting to o365. upstream: - issue: https://gitlab.gnome.org/GNOME/evolution-ews/-/issues/3 - patch: https://gitlab.gnome.org/GNOME/evolution-ews/uploads/ffa7d7a4934cd6bd8b0f44d8c5a47f8f/ews.patch The patch has not yet been merged upstream due to hard code freeze. I've back-ported the patch to evolution-ews 3.36.5 so it could be shipped with Ubuntu LTS. Would be great if you could integrate that and ship it with Ubuntu LTS, so people could benefit already today. ** Affects: evolution-ews (Ubuntu) Importance: Undecided Status: New ** Attachment added: "0001-Contacts-Retrieve-user-S-MIME-certificate.patch" https://bugs.launchpad.net/bugs/1943450/+attachment/5524954/+files/0001-Contacts-Retrieve-user-S-MIME-certificate.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943450 Title: Contacts: Retrieve user S/MIME certificate does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-ews/+bug/1943450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows
Try https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1932328/comments/18 It worked for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1932328/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939746] [NEW] Leaves open window marker on icon in gdm3 favourites sidebar after program has exited
Public bug reported: Frequently leaves an open window marker on the Thunderbird icon in Gnome Desktop favourites sidebar. This is especially prevalent when the program has been launched as the default email client by some other process. Right clicking on the icon brings up the "New window/Compose New Message/Contacts/Remove from favourites/Quit". This menu is unresponsive and cannot be dismissed. This makes Thunderbird unusable. Ubuntu version is Hirsute. ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: gdm3 thunderbird ** Description changed: Frequently leaves an open window marker on the Thunderbird icon in Gnome Desktop favourites sidebar. This is especially prevalent when the program has been launched as the default email client by some other process. Right clicking on the icon brings up the "New window/Compose New Message/Contacts/Remove from favourites/Quit". This menu is unresponsive and cannot be dismissed. This makes Thunderbird unusable. + + Ubuntu version is Hirsute. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939746 Title: Leaves open window marker on icon in gdm3 favourites sidebar after program has exited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1939746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939183] [NEW] nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
Public bug reported: I don't know why this is being generated. The system did it automatically. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-25-generic Date: Wed Aug 4 21:05:46 2021 InstallationDate: Installed on 2020-05-18 (445 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 340.108-0ubuntu5.20.04.2 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: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939183 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1939183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937957] Re: external hyperlink keyboard freeze
** Description changed: When no FireFox windows are currently open and an external hyperlink, - say from a pdf or doc, is used then the created window freezes the - keyboard. New tabs as well as new opened windows experience the same - issue as long as the original window is still open. Windows key + F9 and - Windows key + Shift have no effect. Some of the Ctrl functions still - work in the window/s and the keyboard freeze is only localized to + specifically those opened with Evince, is used then the created window + freezes the keyboard. New tabs as well as new opened windows experience + the same issue as long as the original window is still open. Windows key + + F9 and Windows key + Shift have no effect. Some of the Ctrl functions + still work in the window/s and the keyboard freeze is only localized to FireFox. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 90.0+build1-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.4.0-80.90~18.04.1-generic 5.4.124 Uname: Linux 5.4.0-80-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: denmark1731 F pulseaudio - /dev/snd/pcmC0D0p: denmark1731 F...m pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: denmark1731 F pulseaudio + /dev/snd/pcmC0D0p: denmark1731 F...m pulseaudio BuildID: 20210705185941 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun Jul 25 22:31:20 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:355 DefaultProfileThemes: extensions.sqlite corrupt or missing ExecutablePath: /usr/lib/firefox/firefox ForcedLayersAccel: False IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback InstallationDate: Installed on 2021-01-08 (198 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) IpRoute: - default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 - 169.254.0.0/16 dev wlp2s0 scope link metric 1000 - 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.115 metric 600 + default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 + 169.254.0.0/16 dev wlp2s0 scope link metric 1000 + 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.115 metric 600 ProcEnviron: - LANGUAGE=en_ZA:en - PATH=(custom, user) - XDG_RUNTIME_DIR= - LANG=en_ZA.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_ZA:en + PATH=(custom, user) + XDG_RUNTIME_DIR= + LANG=en_ZA.UTF-8 + SHELL=/bin/bash Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:355 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: - Profile1 (Default) - LastVersion=None/None (Out of date) - Profile0 - LastVersion=90.0/20210705185941 (In use) + Profile1 (Default) - LastVersion=None/None (Out of date) + Profile0 - LastVersion=90.0/20210705185941 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2012 dmi.bios.vendor: Acer dmi.bios.version: V1.08 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire 5733 dmi.board.vendor: Acer dmi.board.version: V1.08 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.08 dmi.modalias: dmi:bvnAcer:bvrV1.08:bd03/21/2012:svnAcer:pnAspire5733:pvrV1.08:rvnAcer:rnAspire5733:rvrV1.08:cvnAcer:ct10:cvrV1.08: dmi.product.family: Intel_Mobile dmi.product.name: Aspire 5733 dmi.product.sku: Calpella_CRB dmi.product.version: V1.08 dmi.sys.vendor: Acer -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937957 Title: external hyperlink keyboard freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1937957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937957] [NEW] external hyperlink keyboard freeze
Public bug reported: When no FireFox windows are currently open and an external hyperlink, say from a pdf or doc, is used then the created window freezes the keyboard. New tabs as well as new opened windows experience the same issue as long as the original window is still open. Windows key + F9 and Windows key + Shift have no effect. Some of the Ctrl functions still work in the window/s and the keyboard freeze is only localized to FireFox. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 90.0+build1-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.4.0-80.90~18.04.1-generic 5.4.124 Uname: Linux 5.4.0-80-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: denmark1731 F pulseaudio /dev/snd/pcmC0D0p: denmark1731 F...m pulseaudio BuildID: 20210705185941 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun Jul 25 22:31:20 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:355 DefaultProfileThemes: extensions.sqlite corrupt or missing ExecutablePath: /usr/lib/firefox/firefox ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2021-01-08 (198 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) IpRoute: default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.115 metric 600 ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:355 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=90.0/20210705185941 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2012 dmi.bios.vendor: Acer dmi.bios.version: V1.08 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire 5733 dmi.board.vendor: Acer dmi.board.version: V1.08 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.08 dmi.modalias: dmi:bvnAcer:bvrV1.08:bd03/21/2012:svnAcer:pnAspire5733:pvrV1.08:rvnAcer:rnAspire5733:rvrV1.08:cvnAcer:ct10:cvrV1.08: dmi.product.family: Intel_Mobile dmi.product.name: Aspire 5733 dmi.product.sku: Calpella_CRB dmi.product.version: V1.08 dmi.sys.vendor: Acer ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937957 Title: external hyperlink keyboard freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1937957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931263] [NEW] hexedit crashes on window resize
Public bug reported: Resizing the konsole window to be smaller using the bottom right hand corner when running hexedit can sometimes result in a crash. In my testing the window starts at around 232x61. I find it easiest to trigger the bug if I make circular resizing movements, but this isn't always required. Reported upstream: https://github.com/pixel/hexedit/issues/51 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: hexedit 1.5-1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Jun 8 14:52:39 2021 InstallationDate: Installed on 2020-05-05 (398 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: hexedit UpgradeStatus: Upgraded to hirsute on 2021-01-26 (132 days ago) ** Affects: hexedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ** Attachment added: "valgrind log file" https://bugs.launchpad.net/bugs/1931263/+attachment/5503160/+files/valgrind-hexedit.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931263 Title: hexedit crashes on window resize To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hexedit/+bug/1931263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928118] Re: cannot enter foreign arch schroot since qemu 1:5.2+dfsg-4
Looking at the attached schroot.debdiff, I'm not sure why this change is also containing a number of changes related to "dchroot" and "dchroot- dsa", two obsolete tools which are unrelated to the qemu issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928118 Title: cannot enter foreign arch schroot since qemu 1:5.2+dfsg-4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/schroot/+bug/1928118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930605] [NEW] new nvidia driver can't install
Public bug reported: Messages during dist-upgrade 18.04 LTS to 20.04.2 LTS installed nvidia-340 package post-installation script subprocess returned error exit status 10 nvidia-331 dependency problems - leaving unconfigured nvidia-340-uvm dependency problems - leaving unconfigured nvidia-libopencl1-340 dependency problems - leaving unconfigured nvidia-opencl-icd-340 dependency problems - leaving unconfigured La mise à niveau a échoué. Votre système pourrait être inutilisable. Une tentative de récupération va maintenant avoir lieu (dpkg --configure -a). 1) Description:Ubuntu 20.04.2 LTS Release:20.04 2) nvidia-340: Installé : 340.108-0ubuntu5.20.04.2 Candidat : 340.108-0ubuntu5.20.04.2 Table de version : *** 340.108-0ubuntu5.20.04.2 500 500 http://fr.archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages 100 /var/lib/dpkg/status 340.108-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages nvidia-331: Installé : 340.108-0ubuntu5.20.04.2 Candidat : 340.108-0ubuntu5.20.04.2 Table de version : *** 340.108-0ubuntu5.20.04.2 500 500 http://fr.archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages 100 /var/lib/dpkg/status 340.108-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages nvidia-340-uvm: Installé : 340.108-0ubuntu5.20.04.2 Candidat : 340.108-0ubuntu5.20.04.2 Table de version : *** 340.108-0ubuntu5.20.04.2 500 500 http://fr.archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages 100 /var/lib/dpkg/status 340.108-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages nvidia-libopencl1-340: Installé : 340.108-0ubuntu5.20.04.2 Candidat : 340.108-0ubuntu5.20.04.2 Table de version : *** 340.108-0ubuntu5.20.04.2 500 500 http://fr.archive.ubuntu.com/ubuntu focal-updates/multiverse amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/multiverse amd64 Packages 100 /var/lib/dpkg/status 340.108-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu focal/multiverse amd64 Packages nvidia-opencl-icd-340: Installé : 340.108-0ubuntu5.20.04.2 Candidat : 340.108-0ubuntu5.20.04.2 Table de version : *** 340.108-0ubuntu5.20.04.2 500 500 http://fr.archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages 100 /var/lib/dpkg/status 340.108-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages 3) What I expected was No error messages 4) but there was error messages NB: Finally the version seems to works ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.33 ProcVersionSignature: Ubuntu 4.15.0-143.147-generic 4.15.18 Uname: Linux 4.15.0-143-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Jun 2 17:52:17 2021 InstallationDate: Installed on 2014-01-03 (2707 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to focal on 2021-06-02 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930605 Title: new nvidia driver can't install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1930605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921484] Re: libedit no longer reads editrc
Same here, mysql command line used to read bindings from .editrc in previous versions of Ubuntu Server, now fails to honor them in 20.04 LTS. Strace confirms that libedit is not opening the file .editrc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921484 Title: libedit no longer reads editrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libedit/+bug/1921484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1922379] Re: scanner not configured
I am deeply sorry, but I am not running hplip under Ubuntu but I'm using openSUSE Leap 15.2; apparently this OS doesn't know the command apport-collect 1922379. An amazing fact is that with the command hp-scan -f ~/temp/output.pdf from the command line, the printer scans a document correctly! The big inconvenance is that I have to set a lot of parameters each time. Op 06-04-2021 om 17:42 schreef Paul White: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. Please execute the following command only once, as it > will automatically gather debugging information, in a terminal: > > apport-collect 1922379 > > When reporting bugs in the future please use apport by using 'ubuntu- > bug' and the name of the package affected. > > You can learn more about this functionality at > https://wiki.ubuntu.com/ReportingBugs. > > ** Package changed: ubuntu => hplip (Ubuntu) > > ** Changed in: hplip (Ubuntu) > Status: New => Incomplete > > ** Changed in: hplip > Status: New => Incomplete > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922379 Title: scanner not configured To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1922379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919003] Re: Network Name Resolution fails with iproute2 4.15.0-2ubuntu1.3
My initial conclusion may not have been correct. I now think that the fix in iproute2 4.15.0-2ubuntu1.3 made the problem more apparent. The Network Name Resolution service is not actually failing. It is being stopped and restarted (based on the logs). So the real problem seems to be a very aggressive approach to restarting the Network Name Resolution service. In our case, the DHCPClient request is not getting a response, yet the Network Name Resolution service is still being restarted. Mar 13 03:43:32 em-vf-ns1 dhclient[3443]: DHCPDISCOVER on nsblk01 to 255.255.255.255 port 67 interval 5 (xid=0xe499a07d) Mar 13 03:43:37 em-vf-ns1 dhclient[3443]: No DHCPOFFERS received. Mar 13 03:43:37 em-vf-ns1 dhclient[3443]: No working leases in persistent database - sleeping. Mar 13 03:43:37 em-vf-ns1 systemd[1]: Stopping Network Name Resolution... Mar 13 03:43:37 em-vf-ns1 systemd[1]: Stopped Network Name Resolution. Mar 13 03:43:37 em-vf-ns1 systemd[1]: Starting Network Name Resolution... Mar 13 03:43:37 em-vf-ns1 systemd[1]: Started Network Name Resolution. Mar 13 03:43:37 em-vf-ns1 systemd[1]: Starting resolvconf-pull-resolved.service... Mar 13 03:43:37 em-vf-ns1 systemd[1]: Started resolvconf-pull-resolved.service. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919003 Title: Network Name Resolution fails with iproute2 4.15.0-2ubuntu1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1919003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919003] [NEW] Network Name Resolution fails with iproute2 4.15.0-2ubuntu1.3
Public bug reported: The following is repeated periodically in the syslog: Feb 28 20:25:02 em-cel1 systemd[1]: Started Network Name Resolution. Feb 28 20:25:02 em-cel1 systemd[1]: Starting resolvconf-pull-resolved.service... Feb 28 20:25:02 em-cel1 systemd[1]: Started resolvconf-pull-resolved.service. Feb 28 20:25:19 em-cel1 systemd[1]: Stopping Network Name Resolution... Feb 28 20:25:19 em-cel1 systemd[1]: Stopped Network Name Resolution. Feb 28 20:25:19 em-cel1 systemd[1]: Starting Network Name Resolution... There is no log anywhere to indicate why the service failed. The service stopped failing when we downgraded iproute2 from 4.15.0-2ubuntu1.3 to 4.15.0-2ubuntu1.1. The DHCPClient seems to be involved in the chain of events. At the same frequency as the service failures, we do an ifup on a non- auto dhcp interface. The ifup results in a DHCP request, which in this case does not get a response (the link to the DHCP server is down. When we stop the process that does the periodic ifup, the service remains up (with iproute2 4.15.0-2ubuntu1.3). ** Affects: iproute2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919003 Title: Network Name Resolution fails with iproute2 4.15.0-2ubuntu1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1919003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917344] [NEW] wayland was installed as a dependancy, tried to fix manually, had to reinstall kubuntu from scratch, now firmware is out of date
Public bug reported: wayland was installed as a dependancy, tried to fix manually, had to reinstall kubuntu from scratch, now firmware is out of date ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.13 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: KDE Date: Mon Mar 1 19:54:06 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RebootRequiredPkgs: linux-image-5.8.0-25-generic linux-image-5.8.0-44-generic SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy kubuntu ubiquity-20.10.13 ** Attachment added: "syslog" https://bugs.launchpad.net/bugs/1917344/+attachment/5471558/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917344 Title: wayland was installed as a dependancy, tried to fix manually, had to reinstall kubuntu from scratch, now firmware is out of date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1917344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915292] [NEW] Missing kernel modules when using linux-kvm
Public bug reported: Have been unable to use the linux-kvm package for our kvm virtual machines, because of missing kernel modules in the linux-modules-*-kvm package(s). The modules that has affected us for now are nfsd and tcp_bbr. Is there any reason they can't be included in the modules for linux-kvm? Or create a new linux-extra-modules-*-kvm package for those modules you deem undeserving to be in the linux-modules-*-kvm package. ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915292 Title: Missing kernel modules when using linux-kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1915292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914101] [NEW] package clamav-freshclam 0.102.4+dfsg-0ubuntu0.20.04.1 failed to install/upgrade: installed clamav-freshclam package post-removal script subprocess returned error exit status 1
Public bug reported: had trouble installing so removed & trying again ProblemType: Package DistroRelease: Ubuntu 20.04 Package: clamav-freshclam 0.102.4+dfsg-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Feb 1 11:23:58 2021 DuplicateSignature: package:clamav-freshclam:0.102.4+dfsg-0ubuntu0.20.04.1 Removing clamav-freshclam (0.102.4+dfsg-0ubuntu0.20.04.1) ... rm: cannot remove '/var/lib/clamav/daily.cvd': Is a directory dpkg: error processing package clamav-freshclam (--remove): installed clamav-freshclam package post-removal script subprocess returned error exit status 1 ErrorMessage: installed clamav-freshclam package post-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2020-12-12 (51 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=91a86c42-1bc2-4baa-8115-4ac7c980fad0 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: clamav Title: package clamav-freshclam 0.102.4+dfsg-0ubuntu0.20.04.1 failed to install/upgrade: installed clamav-freshclam package post-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: clamav (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914101 Title: package clamav-freshclam 0.102.4+dfsg-0ubuntu0.20.04.1 failed to install/upgrade: installed clamav-freshclam package post-removal script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1914101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1085]
(In reply to Jorg K (GMT+1) from comment #52) > Sorry, this is the first bug I'm de-assigning myself from. Not because it's > too hard but because it's not useful. It would be a geek feature and > personally I don't see what it would be good for. Thank you for looking at the bug, but I don't understand your reaction. How is wanting to be able to select text and copy it "a geek feature"? The only thing I can think of is because you're trying to solve the problem in the wrong way, using a complicated geeky menu system. > I'd like to mark this one "wontfix" Why? > There is bug 327621 which I could fix with one of the options I mentioned: > 1) Change existing copy function 2) Have another menu item (wording?). This looks like the same bug for a different component. It also asks to make the text selectable. > Richard, do you prefer to change the existing "Copy Email Address" function > or have another menu item? I think most people who have commented in this and related bugs see menu options as being second best. If the text is selectable you don't need several options for the different combinations of bits of address that you might want to copy, you can just select the bit you need. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1085 Title: selecting text in full header mode fails To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901017] Re: Desktop gradually increases response lag to clicks in 20.04 (Fixed by Alt+F2, "r"))
@venvugt It looked like the bug was closed just due to inactivity, not because it was invalid. I don't have enough information to create a new bug - I was just adding information to this one. I'd suggest re-opening the bug, as keeping the historical information is surely useful? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901017 Title: Desktop gradually increases response lag to clicks in 20.04 (Fixed by Alt+F2, "r")) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1901017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901017] Re: Desktop gradually increases response lag to clicks in 20.04 (Fixed by Alt+F2, "r"))
I also have been encountering this issue. It's happened a few times now - it only happens after my machine has been up for a while. I start to notice it when alt-tab takes a substantial proportion of a second to switch between windows. gnome-shell seems to be taking quite a bit of CPU time (10% to 30% cpu), but that's possibly just normal. I do have a network mount of a NAS drive, but it doesn't appear to be being probed (I would hear the NAS box spin up). I've attached the result of running the following commands: lspci -k > lspcik.txt gsettings list-recursively org.gnome.shell > settings.txt glxinfo > glxinfo.txt journalctl -b0 | tail -100 > journal.txt I see many Javascript type errors in the journal which might have something to do with the issue. As with the original poster, Alt-F2, then r fixed the issue (at least I have a workaround now!) and I don't see the regular JS errors appearing in the journal any more. ** Attachment added: "gnome.bug.zip" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1901017/+attachment/5452889/+files/gnome.bug.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901017 Title: Desktop gradually increases response lag to clicks in 20.04 (Fixed by Alt+F2, "r")) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1901017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880749] Re: python3 virtualenvs include (broken) bundled pip deps
Almost half a year now and the LTS version is still not fixed? This is sad, because it keeps Ansible from bringing out their PPA for focal. I guess most users switching to pip installations will never automatically apply released security patches for it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880749 Title: python3 virtualenvs include (broken) bundled pip deps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-virtualenv/+bug/1880749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907972] [NEW] cannot plugin Wi-fi printer Epson L4160
Public bug reported: Installed official Epson drivers for L4160 Wi-Fi printer. I can add it in Control Center though it doesn't work - when trying to print test page or to print from other applications it raises errors like "can't connect to printer", etc. Epson drivers from Ubuntu repo don't work either. THE SAME Epson drivers work flawlessly on Fedora on another machine WITH THE SAME PRINTER in the same local network. Some messages I got from journalctl -f : ... E [05/Dec/2020:22:09:57 +0300] [CGI] Unable to resolve \"dnssd://EPSON%20L4160%20Series._ipp._tcp.local/?uuid=cfe92100-67c4-11d4-a45f-f8d027443dcc|EPSON L4160 Series\". E [05/Dec/2020:22:09:57 +0300] [CGI] Unable to resolve \"dnssd://EPSON%20L4160%20Series._ipp._tcp.local/?uuid=cfe92100-67c4-11d4-a45f-f8d027443dcc|EPSON L4160 Series\". W [05/Dec/2020:22:21:23 +0300] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'EPSON_L4160_Series-Gray..\' already exists W [05/Dec/2020:22:21:23 +0300] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'EPSON_L4160_Series-RGB..\' already exists E [05/Dec/2020:22:22:47 +0300] [CGI] Unable to resolve \"dnssd://EPSON%20L4160%20Series._ipp._tcp.local/?uuid=cfe92100-67c4-11d4-a45f-f8d027443dcc|EPSON L4160 Series\". W [05/Dec/2020:22:24:13 +0300] CreateProfile failed: org.freedesktop.ColorManager.Profile.Internal:failed to register object: Объект интерфейса org.freedesktop.ColorManager.Profile уже экспортирован как /org/freedesktop/ColorManager/profiles/EPSON_L4160_Series_Gray__ W [05/Dec/2020:22:24:13 +0300] CreateProfile failed: org.freedesktop.ColorManager.Profile.Internal:failed to register object: Объект интерфейса org.freedesktop.ColorManager.Profile уже экспортирован как /org/freedesktop/ColorManager/profiles/EPSON_L4160_Series_RGB__ E [05/Dec/2020:22:29:27 +0300] [Job 3] Unable to queue job for destination "L4160". E [05/Dec/2020:22:31:14 +0300] [CGI] Unable to create PPD file: Could not poll sufficient capability info from the printer (ipp://EPSON%20L4160%20Series._ipp._tcp.local/, ipp://EPSON443DCC.local:631/ipp/print) via IPP! E [05/Dec/2020:22:31:14 +0300] copy_model: empty PPD file E [05/Dec/2020:22:31:14 +0300] [Client 20] Returning IPP server-error-internal-error for CUPS-Add-Modify-Printer (ipp://localhost/printers/L4160) from localhost. W [05/Dec/2020:22:31:53 +0300] CreateProfile failed: org.freedesktop.ColorManager.Profile.Internal:failed to register object: Объект интерфейса org.freedesktop.ColorManager.Profile уже экспортирован как /org/freedesktop/ColorManager/profiles/EPSON_L4160_Series_Gray__ W [05/Dec/2020:22:31:53 +0300] CreateProfile failed: org.freedesktop.ColorManager.Profile.Internal:failed to register object: Объект интерфейса org.freedesktop.ColorManager.Profile уже экспортирован как /org/freedesktop/ColorManager/profiles/EPSON_L4160_Series_RGB__ E [05/Dec/2020:22:32:13 +0300] [Client 37] Returning IPP server-error-not-accepting-jobs for Print-Job (ipp://localhost/printers/EPSON_L4160_Series) from localhost. E [05/Dec/2020:22:44:06 +0300] [CGI] Unable to create PPD file: Could not poll sufficient capability info from the printer (ipp://EPSON%20L4160%20Series._ipp._tcp.local/, ipp://EPSON443DCC.local:631/ipp/print) via IPP! E [05/Dec/2020:22:44:06 +0300] copy_model: empty PPD file E [05/Dec/2020:22:44:06 +0300] [Client 134] Returning IPP server-error-internal-error for CUPS-Add-Modify-Printer (ipp://localhost/printers/L4160) from localhost. E [05/Dec/2020:22:44:42 +0300] [CGI] Unable to create PPD file: Could not poll sufficient capability info from the printer (ipp://EPSON%20L4160%20Series._ipp._tcp.local/, ipp://EPSON443DCC.local:631/ipp/print) via IPP! E [05/Dec/2020:22:44:42 +0300] copy_model: empty PPD file E [05/Dec/2020:22:44:42 +0300] [Client 134] Returning IPP server-error-internal-error for CUPS-Add-Modify-Printer (ipp://localhost/printers/L4160) from localhost. W [05/Dec/2020:22:51:02 +0300] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'EPSON_L4160_Series-Gray..\' already exists W [05/Dec/2020:22:51:02 +0300] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'EPSON_L4160_Series-RGB..\' already exists ... дек 13 19:54:15 ord1-ubuntu org.fedoraproject.Config.Printing[7404]: /usr/share/system-config-printer/scp-dbus-service.py:602: DeprecationWarning: Gdk.threads_enter is deprecated дек 13 19:54:15 ord1-ubuntu org.fedoraproject.Config.Printing[7404]: Gdk.threads_enter () дек 13 19:54:15 ord1-ubuntu kernel: scp-dbus-servic[7407]: segfault at 4 ip 00509bcb sp 7f77dd364ea0 error 6 in python3.8[423000+294000] дек 13 19:54:15 ord1-ubuntu kernel: Code: 89 50 f8 48 89 48 f0 48 89 71 08 5b c3 66 90 f3 0f 1e fa 55 48 8b 4f f0 48 89 fd 48 8b 57 f8 48 8b 41 08 48 83 e2 fc 83 e0 03 <48> 89 0a 48 09 d0 48 89 41 08 48 83 67 f8 01 48 83 7f 20 00 48 c7 дек 13 19:54:23 ord1-ubuntu gnome-control-c[3071]: Source
[Bug 1894045] Re: modpython support missing from Ganglia
Easiest fix is just adding python-dev-is-python2 to build dependencies instead of python2-dev. This creates the magic link that makes the configure script think that python is available. Debian source/build package uses python-dev instead, but that is just a virtual package which ends up being either python-dev-is-python2 or python-dev-is-python3. But python3 does not work since the configure script uses print without parentheses. If one is willing one look into if the python binary is actually needed. Since modpython.so is just a plugin for ganglia it should just use libpython2 and that is what configure should look for. But that might be too much work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894045 Title: modpython support missing from Ganglia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ganglia/+bug/1894045/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849631] Re: package grub-pc 2.04-1ubuntu12 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 1
The error persists after a restart. This is not an expected bahaviour since the xserver is running then. The failed installation is announced at every run of update manager. Also a (re-)configuration brings up this error: dpkg --configure -a OR dpkg --configure grub-pc dpkg: error processing package grub-pc (--configure): installed grub-pc package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: grub-pc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849631 Title: package grub-pc 2.04-1ubuntu12 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1849631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1899414] [NEW] schroot fails for source chroots with 'std:bad_alloc' on groovy
Hi Alex, Looking any https://gitlab.com/codelibre/schroot/-/blame/schroot-1.6/sbuild/sbuild-util.cc#L757 <https://gitlab.com/codelibre/schroot/-/blame/schroot-1.6/sbuild/sbuild-util.cc#L757> and this commit: https://gitlab.com/codelibre/schroot/-/commit/83bc6d3f99b1aa04a4864faeeb867ed09bae8e55 It looks like if this hasn’t been picked up, it should be. Maybe a new schroot point release is in order; schroot isn’t currently a high priority, I’m afraid. Kind regards, Roger -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899414 Title: schroot fails for source chroots with 'std:bad_alloc' on groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/schroot/+bug/1899414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899414] Re: schroot fails for source chroots with 'std:bad_alloc' on groovy
** Bug watch added: Debian Bug tracker #763896 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763896 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899414 Title: schroot fails for source chroots with 'std:bad_alloc' on groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/schroot/+bug/1899414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
RE: [Bug 1899414] [NEW] schroot fails for source chroots with 'std:bad_alloc' on groovy
Hi Alex,This is failing
here:https://gitlab.com/codelibre/schroot/-/blob/schroot-1.6/sbuild/sbuild-util.cc#L757Is
there something unusual about the group being checked? getgrnam_r has
returned ERANGE and schroot increased the buffer size to accommodate this until
it ran out of memory. The cause of failure is clear but the reason is not.Are
you using LDAP, AD or is this all local users and groups?Kind regards,Roger
Leigh
Original message From: Alex Murray
<1899...@bugs.launchpad.net> Date: 12/10/2020 06:20 (GMT+00:00) To:
rle...@codelibre.net Subject: [Bug 1899414] [NEW] schroot fails for source
chroots with
'std:bad_alloc' on groovy Public bug reported:After upgrading to groovy or
installing fresh from the beta, schrootfails to enter a source: chroot with
std:bad_alloc:$ schroot -c source:bionic-amd64E: std::bad_allocRunning this
with debugging symbols under gdb we get the followingbacktrace:amurray@slate:~$
gdb --ex='break std::bad_alloc::bad_alloc()' --ex=run --args schroot -c
source:bionic-amd64GNU gdb (Ubuntu 9.2-0ubuntu2) 9.2Copyright (C) 2020 Free
Software Foundation, Inc.License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>This is free software: you are free to change
and redistribute it.There is NO WARRANTY, to the extent permitted by law.Type
"show copying" and "show warranty" for details.This GDB was configured as
"x86_64-linux-gnu".Type "show configuration" for configuration details.For bug
reporting instructions, please see:<http://www.gnu.org/software/gdb/bugs/>.Find
the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.For help, type "help".Type
"apropos word" to search for commands related to "word"...Reading symbols from
schroot...Reading symbols from
/usr/lib/debug/.build-id/70/4469864df39ed3af1f8a23bd8d27adffeb8315.debug...Catchpoint
1 (throw)Function "std::bad_alloc::bad_alloc()" not defined.Make breakpoint
pending on future shared library load? (y or [n]) yBreakpoint 2
(std::bad_alloc::bad_alloc()) pending.Starting program: /usr/bin/schroot -c
source:bionic-amd64[Thread debugging using libthread_db enabled]Using host
libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".Catchpoint 1
(exception thrown), 0x7fd231965762 in __cxa_throw () from
/lib/x86_64-linux-gnu/libstdc++.so.6(gdb) bt full#0 0x7fd231965762 in
__cxa_throw () from /lib/x86_64-linux-gnu/libstdc++.so.6No symbol table info
available.#1 0x7fd231959562 in ?? () from
/lib/x86_64-linux-gnu/libstdc++.so.6No symbol table info available.#2
0x5596c26b8a2f in __gnu_cxx::new_allocator::allocate
(this=0x7ffd3b189dd0, __n=34359738368) at
/usr/include/c++/9/ext/new_allocator.h:102No locals.#3
std::allocator_traits >::allocate (__a=...,
__n=34359738368) at /usr/include/c++/9/bits/alloc_traits.h:444No locals.#4
std::_Vector_base >::_M_allocate
(this=0x7ffd3b189dd0, __n=34359738368) at
/usr/include/c++/9/bits/stl_vector.h:343No locals.#5 std::vector >::reserve (this=this@entry=0x7ffd3b189dd0,
__n=__n@entry=34359738368) at /usr/include/c++/9/bits/vector.tcc:78
__old_size = 0 __tmp = #6 0x5596c26b5996 in
sbuild::group::query_name (this=0x7ffd3b189db0, name=0x5596c2c558c0 "admin") at
./sbuild/sbuild-util.cc:770 size = 34359738368 error = grp_result = 0x0#7 0x5596c26b5abf in sbuild::group::query_name
(name=..., this=0x7ffd3b189db0) at
/usr/include/c++/9/bits/basic_string.h:2300No locals.#8 sbuild::group::group
(this=0x7ffd3b189db0, name=...) at ./sbuild/sbuild-util.cc:717No locals.#9
0x5596c26a463f in sbuild::session::is_group_member (this=,
groupname="admin") at ./sbuild/sbuild-session.cc:390 grp = { =
{gr_name = 0x7fd1b0416010 , gr_passwd = 0x7fd1b041601e , gr_gid = 138, gr_mem = 0x7fd1b0416028},
buffer = std::vector of length 0, capacity 17179869184, valid = false}
group_member = __PRETTY_FUNCTION__ = #10
0x5596c26a49eb in sbuild::session::get_chroot_membership
(this=0x5596c2c329f0, chroot=..., in_users=@0x7ffd3b189e94: false,
in_root_users=@0x7ffd3b189e95: false, in_groups=@0x7ffd3b189e96: false,
in_root_groups=@0x7ffd3b189e97: true) at ./sbuild/sbuild-session.cc:475
gp = "admin" users = std::vector of length 0, capacity 0
root_users = groups = root_groups
= std::vector of length 3, capacity 3 = {"root", "sbuild", "admin"} upos
= rupos = #11 0x5596c26a4cd1 in
sbuild::session::get_chroot_auth_status (this=0x5596c2c329f0,
status=sbuild::auth::STATUS_NONE, chroot=...) at ./sbuild/sbuild-session.cc:496
in_users = false in_root_users = false in_groups = false
in_root_groups = true#12 0x000
[Bug 1899288] [NEW] Python3 can't co-exist with Oracle's VirtualBox on 20.10
Public bug reported: Sorry I couldn't file this bug against the correct packages. The form told me there are no such packages as python-is-python3 and dh-python in Ubuntu... Release: Groovy Gorilla (Ubuntu 20.10). Package versions: python-is-python3 3.8.2-4 dh-python 4.20200925 The release of Ubuntu 20.10 is less than two weeks out, so I'd like to draw attention to a problem I've run into. It seems that 20.10 defaults to python3 and wants to install python-is-python3, which pulls in the latest version of dh-python, which in turn can't co-exist with Oracle's Virtualbox-6.1 and wants to uninstall it. I don't mind having _both_ python2 (apparently a requirement of VirtualBox) and python3 installed. But as of right now I can have either python-is-python3, and not be able to do a complete upgrade since virtualbox-6.1 will be uninstalled, or python-is-python2, in which case I cripple 20.10's python3 install, since I won't get dh-python and python-six. Ia there something the python packagers do about this? ** Affects: ubuntu Importance: Undecided Status: New ** Tags: 20.10 dh-python python-is-python3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899288 Title: Python3 can't co-exist with Oracle's VirtualBox on 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1899288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891680] Re: grub-pc needs to detect when debconf points to invalid drive and stop in preinst, before unpacking files, and also treat this as a failure in postinst
Upgrade (from v18.04 to 20.04) is already released! Thanks to everybody for your debbuging and support! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891680 Title: grub-pc needs to detect when debconf points to invalid drive and stop in preinst, before unpacking files, and also treat this as a failure in postinst To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1891680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864203] Re: 'image add project' fails to find project for non-admin user
This may have been fixed already by this commit: https://opendev.org/openstack/osc- lib/commit/1ff3720daefd98a77557e5692fd7052b5930ae6c Revert "Add error message when occurrence Forbidden error" This reverts commit 3c0559def3. This patch is breaking the Glance image share function. Change-Id: Ic380b4fdeb334b70be39fcf07670902c0bc89dd9 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864203 Title: 'image add project' fails to find project for non-admin user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-openstackclient/+bug/1864203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887223] Re: python3-openimageio fails with an ImportError: libjemalloc.so.2: cannot allocate memory in static TLS block
*** This bug is a duplicate of bug 1882998 *** https://bugs.launchpad.net/bugs/1882998 Also, it's not clear about the duplicated bug. That one is for OpenVDB, not OpenImageIO as here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887223 Title: python3-openimageio fails with an ImportError: libjemalloc.so.2: cannot allocate memory in static TLS block To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openimageio/+bug/1887223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887223] Re: python3-openimageio fails with an ImportError: libjemalloc.so.2: cannot allocate memory in static TLS block
*** This bug is a duplicate of bug 1882998 *** https://bugs.launchpad.net/bugs/1882998 Ugh, what good is the LTS then... yikes? Should I just get the groovy package of python3-openimageio and have it work correctly? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887223 Title: python3-openimageio fails with an ImportError: libjemalloc.so.2: cannot allocate memory in static TLS block To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openimageio/+bug/1887223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887223] [NEW] python3-openimageio fails with an ImportError: libjemalloc.so.2: cannot allocate memory in static TLS block
Public bug reported: Trying to use the python3-openimageio package inside python3 fails with the following problem: ```Shell $ python3 Python 3.8.2 (default, Apr 27 2020, 15:53:34) [GCC 9.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import OpenImageIO Traceback (most recent call last): File "", line 1, in ImportError: /lib/x86_64-linux-gnu/libjemalloc.so.2: cannot allocate memory in static TLS block ``` Repro steps: - Have Ubuntu 20.04 LTS installed - sudo apt install python3-openimageio - Attempt to import the OpenImageIO module ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: python3-openimageio 2.1.12.0~dfsg0-1 ProcVersionSignature: User Name 5.4.0-1020.20-azure 5.4.44 Uname: Linux 5.4.0-1020-azure x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Jul 11 09:34:05 2020 SourcePackage: openimageio UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openimageio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887223 Title: python3-openimageio fails with an ImportError: libjemalloc.so.2: cannot allocate memory in static TLS block To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openimageio/+bug/1887223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
The working around is working adequately for me:
Jul 02 08:50:59 lenny gnome-shell[17639]: Enabling experimental feature
'x11-randr-fractional-scaling'
Jul 02 08:50:59 lenny gnome-shell[17639]: Crtc at 0.00x2160.00 size
1920.00x1080.00 (@ 2.00 - adapted 2.00) considering it of
3840.00x2160.00
Jul 02 08:50:59 lenny gnome-shell[17639]: Crtc at 0.00x0.00 size
1920.00x1080.00 (@ 2.00 - adapted 2.00) considering it of
3840.00x2160.00
Jul 02 08:50:59 lenny gnome-shell[17639]: Setting screen size 3840x4320
Jul 02 08:50:59 lenny gnome-shell[17639]: Setting screen size to 3840x4320
Jul 02 08:50:59 lenny gnome-shell[17639]: Scaling at 1.00 (transformation
matrix is 65536 = 1.00) using filter fast
Jul 02 08:50:59 lenny gnome-shell[17639]: Configuring CRTC 504 with mode 509
(3840 x 2160 @ 59.999294) at position 0, 2160 and transform 0
Jul 02 08:50:59 lenny gnome-shell[17639]: Setting UBUNTU crtc config crtc 504,
timestamp 0 (config timestamp 158041), x: 0, y: 2160, mode: 509, rotation 1,
n_outputs 1: RETURN reply 0x56264b3d7970, error: (nil)
Jul 02 08:50:59 lenny gnome-shell[17639]: Scaling at 1.00 (transformation
matrix is 65536 = 1.00) using filter fast
Jul 02 08:50:59 lenny gnome-shell[17639]: Configuring CRTC 441 with mode 448
(3840 x 2160 @ 60.00) at position 0, 0 and transform 0
Jul 02 08:50:59 lenny gnome-shell[17639]: Setting UBUNTU crtc config crtc 441,
timestamp 0 (config timestamp 158041), x: 0, y: 0, mode: 448, rotation 1,
n_outputs 1: RETURN reply 0x56264b3d7970, error: (nil)
Jul 02 08:51:00 lenny gnome-shell[17639]: Unset XDG_SESSION_ID,
getCurrentSessionProxy() called outside a user session. Asking logind directly.
Jul 02 08:51:00 lenny gnome-shell[17639]: Will monitor session 2
Jul 02 08:51:00 lenny gnome-shell[17639]: Telepathy is not available, chat
integration will be disabled.
Jul 02 08:51:00 lenny gnome-shell[17639]: Setting screen size 3840x4320
Jul 02 08:51:00 lenny gnome-shell[17639]: Setting screen size 3840x4320
Jul 02 08:51:00 lenny gnome-shell[17639]: Setting screen size 3840x4320
Jul 02 08:51:00 lenny gnome-shell[17639]: Setting screen size 3840x4320
Jul 02 08:51:00 lenny gnome-shell[17639]: Error looking up permission:
GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
Jul 02 08:51:02 lenny gnome-shell[17639]: GNOME Shell started at Thu Jul 02
2020 08:51:00 GMT-0400 (EDT)
Jul 02 08:51:02 lenny gnome-shell[17639]: Registering session with GDM
Jul 02 08:52:08 lenny gnome-shell[17639]: polkitAuthenticationAgent: Received
2identities that can be used for authentication. Only considering one.
Jul 02 08:52:23 lenny gnome-shell[17639]:
../clutter/clutter/clutter-actor.c:10556: The clutter_actor_set_allocation()
function can only be called from within the implementation of the
ClutterActor::allocate() virtual function.
Jul 02 08:52:28 lenny gnome-shell[17639]: GOt configuration change [(0, 2160,
1.0, uint32 0, false, [('eDP-1-1', '3840x2160@59.999294281005859',
{'underscanning': })]), (0, 0, 2.0, 0, true, [('HDMI-0', '3840x2160@60',
{'underscanning': })])]
Jul 02 08:52:29 lenny gnome-shell[17639]: GOt configuration change [(0, 2160,
1.0, uint32 0, false, [('eDP-1-1', '3840x2160@59.999294281005859',
{'underscanning': })]), (0, 0, 2.0, 0, true, [('HDMI-0', '3840x2160@60',
{'underscanning': })])]
Jul 02 08:52:29 lenny gnome-shell[17639]: GOt configuration change [(0, 2160,
1.0, uint32 0, false, [('eDP-1-1', '3840x2160@59.999294281005859',
{'underscanning': })]), (0, 0, 2.0, 0, true, [('HDMI-0', '3840x2160@60',
{'underscanning': })])]
Jul 02 08:52:30 lenny gnome-shell[17639]: GOt configuration change [(0, 2160,
1.0, uint32 0, false, [('eDP-1-1', '3840x2160@59.999294281005859',
{'underscanning': })]), (0, 0, 1.0, 0, true, [('HDMI-0', '3840x2160@60',
{'underscanning': })])]
Jul 02 08:52:32 lenny gnome-shell[17639]: GOt configuration change [(0, 2160,
1.0, uint32 0, false, [('eDP-1-1', '3840x2160@59.999294281005859',
{'underscanning': })]), (0, 0, 1.0, 0, true, [('HDMI-0', '3840x2160@60',
{'underscanning': })])]
Jul 02 08:52:32 lenny gnome-shell[17639]: Setting screen size 3840x4320
Jul 02 08:53:36 lenny gnome-shell[17639]: GOt configuration change [(0, 2880,
1.0, uint32 0, false, [('eDP-1-1', '3840x2160@59.999294281005859',
{'underscanning': })]), (0, 0, 1.5, 0, true, [('HDMI-0', '3840x2160@60',
{'underscanning': })])]
Jul 02 08:53:36 lenny gnome-shell[17639]: GOt configuration change [(0, 2880,
1.0, uint32 0, false, [('eDP-1-1', '3840x2160@59.999294281005859',
{'underscanning': })]), (0, 0, 1.5, 0, true, [('HDMI-0', '3840x2160@60',
{'underscanning': })])]
Jul 02 08:53:36 lenny gnome-shell[17639]: GOt configuration change [(0, 2880,
1.0, uint32 0, false, [('eDP-1-1', '3840x2160@59.999294281005859',
{'underscanning': })]), (0, 0, 1.5, 0, true, [('HDMI-0', '3840x2160@60',
{'underscanning': })])]
Jul 02 08:53:38 lenny gnome-shell[17639]: GOt
[Bug 1736222] Re: speech-dispatcher distorts all sound
I have the same problem. Killing speech-dispatcher fixes this, but I want to keep it available. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1736222 Title: speech-dispatcher distorts all sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1736222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762978] Re: ksmserver-logout-greeter crashes on logout preventing me from logging out
I have just experienced this on Kubuntu 20.04. I have an nvidia card and apt just upgraded the nvidia drivers. I wonder if that is related. After the upgrade, blender refuses to start, stating that there is no supported graphics card so *something* has changed there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762978 Title: ksmserver-logout-greeter crashes on logout preventing me from logging out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1762978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872796] Re: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled
Daniel, I apologise. We have been talking about different apps. I have been referring to the browser plugin that talks to https://extensions.gnome.org/. This is because it was the first thing I spotted when I searched on the net. I realise that what you have been talking about the is a standalone app that is accessible via the applications panel or the activities search box. Yes, the standalone app works perfectly and is packaged with the shell. The browser plugin does not. I have only tested the Firefox version though. The Chrome one might be better. Thank you for being patient Roger -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872796 Title: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872796] Re: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled
I am running Ubuntu Focal 20.04. The gnome-shell version is 3.36.2-1ubuntu1-20.04.1. The desktop icons version is 20.04.0-2-1ubuntu1-20.04.1. The app does not work. I believe the app is designed to work on per user extensions only. The desktop icon extension is installed as a system extension in /usr/share/gnome-shell/extensions. See the review by akram87 on the page https://extensions.gnome.org/extension/1465/desktop-icons/ But that is not the point. All I am trying to achieve is to gather information about the impact the ubuntu version of the extension has on the desktop rendering. The easiest way for the user to do this is by issuing one simple command. sudo mv /usr/share/gnome-shell/extensions/desktop-icons@csoriano something-else If I am missing something here please accept my apologies. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872796 Title: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872796] Re: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled
The Extensions app does not appear to work fro the csoriano version of desktop icons. It thinks that it is the rastersoft fork. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872796 Title: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867585] Re: CPU spikes caused by saving PDF to Desktop
If you are experiencing this bug. Try the following. if the directory "/usr/share/gnome-shell/extensions/desktop- icons@csoriano" rename it to something else. Then restart the desktop (logout then login). Please report the results of this test back here. I am trying to correlate information on the part this extension is playing in various desktop rendering glitches. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867585 Title: CPU spikes caused by saving PDF to Desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1867585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872796] Re: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled
If you are experiencing this bug. Try the following. if the directory "/usr/share/gnome-shell/extensions/desktop- icons@csoriano" rename it to something else. Then restart the desktop (logout then login). Please report the results of this test back here. I am trying to correlate information on the part this extension is playing in various desktop rendering glitches. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872796 Title: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832812] Re: Locking and unlocking the screen is slow and stuttery
If you are experiencing this bug. Try the following. if the directory "/usr/share/gnome-shell/extensions/desktop- icons@csoriano" rename it to something else. Then restart the desktop (logout then login). Please report the results of this test back here. I am trying to correlate information on the part this extension is playing in various desktop rendering glitches. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832812 Title: Locking and unlocking the screen is slow and stuttery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812883] Re: Desktop view flashes every time ~/Desktop changes
This bug is still present in Focal. It seems to have lost focus in upstream. In Focal it is much harder to remove the extension as it is even more tightly linked in as a mandatory dependency for a number of major system components. The only way to remove it is by deleting or renaming its files. It seems to me that this extension is responsible for numerous performance issues. A number of bugs have been raised on different symptoms, but all have a common factor of impacting performance and involving this extension. May I suggest that an umbrella bug is created and named something like "Unacceptable Gnome shell perfomance" and marked as critical. The first priority is to make this extension optional and disabled by default. The process of enabling should warn of potential performance issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812883 Title: Desktop view flashes every time ~/Desktop changes To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1812883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 677139] Fwd:
�� �� �� �� https://bitly.com/3ffH1ws �� �� �� From: natopeacekeeper Sent: Saturday, June 13, 2020 12:39:09 PM To: 677...@bugs.launchpad.net Subject: �� http://www.bing.com/search?q==FUBMECYDTFWTZQW=QCBWHHWYPBMMYFZ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/677139 Title: [Realtek ID 275] Recording problem intenal micphone , internal laptop speacker no not work., however when you use speacker or micphone via jacks external audio works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/677139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880347] Re: Permanent pointer arrow at center of screen
Unfortunately, after a recent restart, the problem has returned, and my prior trick of changing the Refresh Rate no longer fixes the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880347 Title: Permanent pointer arrow at center of screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1880347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1736222] Re: speech-dispatcher distorts all sound
I have the same experience as Comment #14 - on a fresh install of 20.04 LTS, this problem randomly (at least it seems random) occurs and is fixed by killing speech-dispatcher. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1736222 Title: speech-dispatcher distorts all sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1736222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880347] Re: Permanent pointer arrow at center of screen
Changing the Displays "Scale" and toggling "Adjust for TV" did not fix the problem. However, changing the Refresh Rate from 60.00 Hz to 59.94 Hz fixed the problem, and when I changed the Refresh Rate back to 60.00 Hz, the problem remained fixed (i.e., no permanent pointer arrow). This bug could be perhaps related to this old bug: https://askubuntu.com/questions/598096/14-04-second-mouse-pointer-stuck- in-middle-of-the-screen -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880347 Title: Permanent pointer arrow at center of screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880347] Re: Permanent pointer arrow at center of screen
Restarting the system does not fix the problem nor does changing the background. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880347 Title: Permanent pointer arrow at center of screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880347] [NEW] Permanent pointer arrow at center of screen
Public bug reported: There is a permanent pointer arrow on my screen. I have included a screenshot. The pointer arrow in the center of the screen is *not* my mouse pointer. My mouse pointer functions normally but I can't get rid of the pointer arrow in the center of the screen. I have not tried restarting the system to see if it goes away as I wanted to file this bug first. OS Name: Ubuntu 20.04 LTS OS Type: 64-bit GNOME Version: 3.36.2 Windowing System: X11 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 23 17:07:19 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Nitro+ Radeon RX 570/580/590 [1da2:e366] InstallationDate: Installed on 2020-05-23 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=2fd43526-0b59-4c37-890d-023522b1288c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.10 dmi.board.name: AB350M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.10:bd08/30/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Attachment added: "Picture of permanent pointer arrow (near center of screen)." https://bugs.launchpad.net/bugs/1880347/+attachment/5375999/+files/Screenshot%20from%202020-05-23%2017-12-12.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880347 Title: Permanent pointer arrow at center of screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877090] [NEW] Help users who have started the installer in the wrong efi/bios mode
Public bug reported: I recently tried to do a fresh install of Kubuntu 20.04 over the top of an existing installation. sda - Windows install sdb - Windows spinning disk sdc - Linux disk, partitioned into / and /home Because I didn't want to trash /home, I had to choose manual partitioning. I set sdc1 to be formatted ext4 and mounted at /, set sdc2 to be mounted as /home, and set the boot loader to be installed on sdc. I'm not convinced the partitioning part is relevant. After the installation finished and I rebooted, I was presented with a grub terminal, nothing else. I eventually realised that I had booted the usb stick into bios mode (this was the first entry I found), and when I repeated the installation with it booted into uefi mode everything worked. I don't know anything about the details of bios/uefi, so this may be a stupid question, but is there any way that the installer could have figured out that I was doing something wrong and given me a hint before I rebooted to a grub console? I haven't tested with automatic partitioning, maybe that works better, but booting to a blank grub console is a pretty harsh outcome for the installer. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877090 Title: Help users who have started the installer in the wrong efi/bios mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1877090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876889] Re: Jiggling Frequent/All/page buttons at low resolutions
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2758 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2758 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2758 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876889 Title: Jiggling Frequent/All/page buttons at low resolutions To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1876889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876889] [NEW] Jiggling UI elements at low resolutions
Public bug reported: I installed 20.04 stock to VirtualBox and clicking the "3x3 grid of dots" button bottom left of the desktop brings up applications to chose from, but the "Frequent All" UI elements are jiggling up and down. This only seems to happen at 800x600. https://www.youtube.com/watch?v=4NIz0UCA4So ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 5 10:38:05 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-05 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876889 Title: Jiggling UI elements at low resolutions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871805] Re: --wait option not working as expected (3.28)
Thank you, I have just updated the description. Should I try to make the fix and upload a debdiff which includes all libraries upgrades? ** Description changed: + [Impact] + + Users are unable to launch an asynchronous gnome-terminal. In some + cases, a user/program/script might want to run a gnome-terminal with a + provided command and wait till the launched gnome-terminal exits. + + By default, gnome-terminal runs synchronously as it uses the gnome- + server to handle the requests. To solve that, gnome-terminal 3.27.1 + introduced the --wait option which solves this issue. The problem, is + that --wait flag does not work properly till version >= 3.36 which also + uses a new vte version (libvte-2.91-dev_0.60.1). Thus users cannot wait + for a gnome-terminal session process to finish. + + More information: https://gitlab.gnome.org/GNOME/gnome- + terminal/issues/16 + + [Test Case] + + To reproduce the bug let's assume that we want to open a gnome-terminal + with a provided command, for example a simple bash: + + 1- Open a terminal: + + gnome-terminal -- /bin/sh -c "/bin/bash" + + This will launch gnome-terminal with a bash but the parent process in + the first terminal finishes just after executing the command, even if + the gnome-terminal is opened. + + 2- Include the --wait option to make the command call asynchronous: + + gnome-terminal --wait -- /bin/sh -c "/bin/bash" + + - Now you can see int the first terminal that the processes didn't + finish, instead it is waiting for the launched gnome-terminal. + + To see the explained bug try to close the opened gnome-terminal using + the X icon windows or File-> Close Tab. => The parent process in + terminal 1 does not receive the child-exited signal, thus it keeps + waiting forever. + + However if we try to exit from the launched gnome-terminal by typing + "exit" on it, the parent process does receive the corresponding signal. + + [Regression Potential] + + As mentioned before, this bug was solved in gnome-terminal >= 3.36 + Many users use the GUI options in order to finish a process, so this bug prevents developers to take advantage of the --wait option in its programs. + + The version 3.36 is included in new Ubuntu versions but not in the + bionic one(Ubuntu 18.04). Many users and enterprises are still using + Ubuntu 18.04 as the new LTS has just been released a few days ago. + + [Other Info] + + Initial bug report: + Dear Maintainers, We have developed a program that it launches a new gnome-terminal with a ssh tunnel connection. Basically, the program forwards a local port to the destination address and opens a new terminal with a ssh connection to the local port: gnome-terminal -e "/usr/bin/ssh -o XXX -p XXX ubuntu@127.0.0.2" The problem comes when we need to know when this gnome-terminal session has finished, in order to end the tunnel process. As you might know, the gnome-terminal command fires up gnome-terminal-server which it might be already running. Who handles the "ssh" connection is the gnome-terminal- server and not the gnome-terminal command, thus our program receives and exit code just after executing the previous command. In previous version there was the --disable-factory option, but unfortunately now is deprecated. Because of this type of problem it was added the --wait flag which was introduced in 3.27.1: gnome-terminal --wait -e "/usr/bin/ssh -o XXX -p XXX ubuntu@127.0.0.2" - Nevertheless, there's a bug in this version. More information: - https://gitlab.gnome.org/GNOME/gnome-terminal/issues/16 + Nevertheless, there's a bug in this version. You can reproduced by launching a new gnome-terminal with the --wait flag from a gnome-terminal session and try to close it via a window operation. In that version --wait only works if with the exit command in the opened session. As mentioned in the linked URL this is solved in version >= 3.36 which also uses a new vte version (libvte-2.91-dev_0.60.1). I have seen that there are multiple issues referring the --disable-factory deprecated option, those could be closed as the new --wait option has the same behavior. Shall we update the libvte version used by gnome? The last libvte version has the proper child exit SIGNAL handler which solves the described issue. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.28.1-1ubuntu1 Architecture: amd64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871805 Title: --wait option not working as expected (3.28) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1871805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876138] [NEW] new VLC icon appears among "Gnome Shell Extension" icons
Public bug reported: new VLC icons appear among "Gnome Shell Extension" icons Ubuntu 20.04 AMD64 Gnome 3.36.1 X11 VLC installed from "Ubuntu Software" version 3.0.10 updated 2010-04-03 (snapcraft.io) new VLC icon appears at every execution of VLC (execution-watch video-close VLC then repeat) cannot remove VLC icons in any way VLC icon does not re-appear after re-boot ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: vlc (not installed) ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 11:51:45 2020 InstallationDate: Installed on 2020-04-09 (21 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: vlc UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876138 Title: new VLC icon appears among "Gnome Shell Extension" icons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1876138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871805] Re: --wait option not working as expected (3.28)
** Summary changed: - Update g-t 3.36 version to solve --wait issue(bionic) + --wait option not working as expected (3.28) ** Description changed: Dear Maintainers, - - We have developed a program that it launches a new gnome-terminal with a ssh tunnel connection. Basically, the program forwards a local port to the destination address and opens a new terminal with a ssh connection to the local port: - + We have developed a program that it launches a new gnome-terminal with a + ssh tunnel connection. Basically, the program forwards a local port to + the destination address and opens a new terminal with a ssh connection + to the local port: gnome-terminal -e "/usr/bin/ssh -o XXX -p XXX ubuntu@127.0.0.2" The problem comes when we need to know when this gnome-terminal session has finished, in order to end the tunnel process. As you might know, the gnome-terminal command fires up gnome-terminal-server which it might be already running. Who handles the "ssh" connection is the gnome-terminal- server and not the gnome-terminal command, thus our program receives and exit code just after executing the previous command. In previous version there was the --disable-factory option, but unfortunately now is deprecated. Because of this type of problem it was added the --wait flag which was introduced in 3.27.1: gnome-terminal --wait -e "/usr/bin/ssh -o XXX -p XXX ubuntu@127.0.0.2" - - Nevertheless, there's a bug in this version. More information: https://gitlab.gnome.org/GNOME/gnome-terminal/issues/16 + Nevertheless, there's a bug in this version. More information: + https://gitlab.gnome.org/GNOME/gnome-terminal/issues/16 You can reproduced by launching a new gnome-terminal with the --wait flag from a gnome-terminal session and try to close it via a window operation. In that version --wait only works if with the exit command in the opened session. As mentioned in the linked URL this is solved in version >= 3.36 which also uses a new vte version (libvte-2.91-dev_0.60.1). I have seen that there are multiple issues referring the --disable-factory deprecated option, those could be closed as the new --wait option has the same behavior. - Could we update the bionic gnom-terminal 3.28 to >= 3.36 version? + Shall we update the libvte version used by gnome? The last libvte + version has the proper child exit SIGNAL handler which solves the + described issue. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.28.1-1ubuntu1 Architecture: amd64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871805 Title: --wait option not working as expected (3.28) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1871805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869568] Re: Unlock takes a long time
See https://github.com/home-sweet-gnome/dash-to-panel/issues/959, wherein I discover that dash-to-panel seems to be the worst offender in terms of leaking handlers, but there's a lower-grade steady leak anyway, which might bear looking at. ** Bug watch added: github.com/home-sweet-gnome/dash-to-panel/issues #959 https://github.com/home-sweet-gnome/dash-to-panel/issues/959 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869568 Title: Unlock takes a long time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869568] Re: Unlock takes a long time
> see if something's leaking registered handlers. It looks like clutter handlers are stored in two different hash tables: g_handlers and g_handler_list_bsa_ht. On the PC that's really slow, g_handlers.size = 8388608 (that's ~8M); on the PC that's not, g_handlers.size = 65536 (~65K). So, yeah, something's leaking, afaict. Gonna see if the hash table entries (signal_id, instance, closure) point to anything that gives me a clue. Given that the extensions are written mostly in JS, this is gonna be all kinds of interesting... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869568 Title: Unlock takes a long time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869568] Re: Unlock takes a long time
This is proving to be really difficult to reproduce -- it's getting slower (but really slowly) on my spare PC. The memory use for gnome- shell is, essentially, static. So: I sampled some perf data from the PC where it consistently happens and threw up a flame graph. It spends a bunch of time in 'clutter_actor_destroy' -> 'destroy_closure_array' -> 'handler_lookup'. This suggests to me that some extension or other is registering a handler for something multiple times, and not cleaning it up, which means it takes longer and longer to iterate through the list of handlers. I'm gonna have a rummage through the source code to see which function adds handlers, and then I'll attach a debugger to it to see if something's leaking registered handlers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869568 Title: Unlock takes a long time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1483414] Re: G_Ticker: Consistency failure during network play
"caused because server and client uses different IWAD files" - Not in my case -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1483414 Title: G_Ticker: Consistency failure during network play To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/prboom-plus/+bug/1483414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871805] Re: Update g-t 3.36 version to solve --wait issue(bionic)
** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871805 Title: Update g-t 3.36 version to solve --wait issue(bionic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1871805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871805] [NEW] Update g-t 3.36 version to solve --wait issue(bionic)
Public bug reported: Dear Maintainers, We have developed a program that it launches a new gnome-terminal with a ssh tunnel connection. Basically, the program forwards a local port to the destination address and opens a new terminal with a ssh connection to the local port: gnome-terminal -e "/usr/bin/ssh -o XXX -p XXX ubuntu@127.0.0.2" The problem comes when we need to know when this gnome-terminal session has finished, in order to end the tunnel process. As you might know, the gnome-terminal command fires up gnome-terminal-server which it might be already running. Who handles the "ssh" connection is the gnome-terminal- server and not the gnome-terminal command, thus our program receives and exit code just after executing the previous command. In previous version there was the --disable-factory option, but unfortunately now is deprecated. Because of this type of problem it was added the --wait flag which was introduced in 3.27.1: gnome-terminal --wait -e "/usr/bin/ssh -o XXX -p XXX ubuntu@127.0.0.2" Nevertheless, there's a bug in this version. More information: https://gitlab.gnome.org/GNOME/gnome-terminal/issues/16 You can reproduced by launching a new gnome-terminal with the --wait flag from a gnome-terminal session and try to close it via a window operation. In that version --wait only works if with the exit command in the opened session. As mentioned in the linked URL this is solved in version >= 3.36 which also uses a new vte version (libvte-2.91-dev_0.60.1). I have seen that there are multiple issues referring the --disable-factory deprecated option, those could be closed as the new --wait option has the same behavior. Could we update the bionic gnom-terminal 3.28 to >= 3.36 version? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.28.1-1ubuntu1 Architecture: amd64 ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871805 Title: Update g-t 3.36 version to solve --wait issue(bionic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1871805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869568] Re: Unlock takes a long time
With ALL extensions, it doesn't get slower. When it was getting slower, I had the standard 'gnome-shell-extensions' package installed. I'm going to reinstall it and see if that reproduces the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869568 Title: Unlock takes a long time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869568] Re: Unlock takes a long time
That should say "With ALL extensions uninstalled..." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869568 Title: Unlock takes a long time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
