Re: [Bug 2068738] Re: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen

[Pete Orlando]

The 7/17/24 update fixed my problem. Thank You Linux Team !


On Wed, Jul 17, 2024 at 9:35 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 the bug
> report.
> 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 
>   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

[Pete Orlando]

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/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 

Re: [Bug 2068738] Re: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen

[Pete Orlando]

Still waiting for update, July 12 2024.


On Wed, Jul 10, 2024 at 4:55 AM Michael Leetz <2068...@bugs.launchpad.net>
wrote:

> Thank you for your effort.
>
> When the update will be available officially?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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 
>   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 test kernel, your system should boot successfully.
>
>   [Where problems could occur]
>
>   We are reverting a problematic patch and going back to how it was
>   before 5.15.0-112-generic. This should not cause any issues for users.
>
>  

Re: [Bug 2068738] Re: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen

[Pete Orlando]

problem still exists after running your instructions. I am still only able
to boot live by booting into the 107.

On Thu, Jul 4, 2024 at 3:20 PM Matthew Ruffell <2068...@bugs.launchpad.net>
wrote:

> Thanks for testing Matt, H.A.
>
> I marked the bug as verified. We should be all good for a release to
> -updates
> early next week. I'll write a new message as soon as the kernel has been
> released for everyone.
>
> Thanks,
> Matthew
>
> ** Tags removed: verification-needed-jammy-linux
> ** Tags added: verification-done-jammy-linux
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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 
>   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:

Re: [Bug 2068738] Re: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen

[Pete Orlando]

Still no fix as of July 1, 2024. Have to boot manually with the 107 to get
my Acer laptop up and running. Hope someone can fix this problem soon.
Thanks for all the hard work on this issue.

On Mon, Jul 1, 2024 at 8:10 AM Daniel <2068...@bugs.launchpad.net>
wrote:

> Did I understand correctly that this bug will be fixed after kernel
> 5.15.0-113?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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 
>   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 test kernel, your system should boot successfully.
>
>   [Where problems could occur]
>
>   

Re: [Bug 2068738] Re: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen

[Pete Orlando]

How do we fix this?

On Tue, Jun 18, 2024 at 9:40 AM Acru <2068...@bugs.launchpad.net> wrote:

> Hey,
> After disabling the kernel update via the update manager, it now got
> installed again, again resulting in a not working system.
> Isn't it possible to just completely remove this one version from the repo?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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 
>   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 test kernel, your system should boot successfully.
>
>   [Where problems could occur]
>
>   We are reverting a problematic patch 

Re: [Bug 2068738] Re: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen

[Pete Orlando]

Hi Matthew, I have an Acer Aspire 5 and running Linux Mint 21.2 Victoria
base: Ubuntu 22.04 jammy with AMD Ryzen 7 3700U with Radeon Vega.
I get the Black screen on boot after installing updates about a week ago.
will there be an update
that will come through the normal update manager ? I don't have programming
skills like many users
of Linux so that would much appreciated. Thank You !

On Thu, Jun 13, 2024 at 8:25 PM Matthew Ruffell <2068...@bugs.launchpad.net>
wrote:

> Hi everyone,
>
> An update:
>
> Greg KH has picked up the patch and added it to upstream stable now:
>
> https://lore.kernel.org/amd-gfx/2024061223-suitable-handler-b6f2@gregkh/
> https://lore.kernel.org/amd-gfx/2024061239-rehydrate-flyable-343e@gregkh/
>
> I suppose we can drop the UBUNTU: SAUCE tags.
>
> I talked to Stefan Bader on the Kernel Team. His current feeling is that
> they might respin the -generic kernels before the release of the current
> cycle (2024.06.10 as per https://kernel.ubuntu.com/) but they are still
> unsure. They might see what else comes up this cycle before they decide.
>
> I'll follow up with the Kernel Team in a couple days.
>
> Thanks,
> Matthew
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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:
>   In Progress
>
> 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 
>   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 

[Bug 2028044] Re: package xrdp 0.9.21.1-1 failed to install/upgrade: installed xrdp package post-installation script subprocess returned error exit status 126

[Pete Loader]

Hi Lenin, thanks for contacting me. I moved on to Ubuntu 24.04 and the issue is 
fixed. Please feel free to close the case
Pete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2028044

Title:
  package xrdp 0.9.21.1-1 failed to install/upgrade: installed xrdp
  package post-installation script subprocess returned error exit status
  126

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/2028044/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970586] Re: No sound support on Linux AWS/Azure kernels (but supported on GCP)

[Pete Woods]

** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970586

Title:
  No sound support on Linux AWS/Azure kernels (but supported on GCP)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1970586/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970586] Re: No sound support on Linux AWS kernel (but supported on GCP)

[Pete Woods]

This appears to work with my simple script, and now pass the tests in
the customer's MIDI library.

Thanks very much for your time here!


> mocha test/unit/*.js && node test/virtual-loopback-test-automated.js


  midi.Input
✔ should raise when not called with new
✔ should be an emitter
.getPortCount
  ✔ .getPortCoun should return an integer
.getPortName
  ✔ requires an argument
  ✔ requires an integer

MidiInAlsa::getPortName: error looking for port name!

  ✔ returns an empty string for unknown port
.openPort
  ✔ requires an argument
  ✔ requires an integer
  ✔ requires a valid port
.openVirtualPort
  ✔ requires an argument
  ✔ requires a string
.on('message')
  ✔ allows promises to resolve

  midi.Output
✔ should raise when not called with new
✔ should not be an emitter
.getPortCount
  ✔ should return an integer
.getPortName
  ✔ requires an argument
  ✔ requires an integer

MidiOutAlsa::getPortName: error looking for port name!

  ✔ returns an empty string for unknown port
.openPort
  ✔ requires an argument
  ✔ requires an integer
  ✔ requires a valid port
.openVirtualPort
  ✔ requires an argument
  ✔ requires a string
.closePort
  ✔ allows you to close a port that was not opened
.send
  ✔ should require an array argument
.sendMessage
  ✔ should require an array argument


  26 passing (61ms)

Enumerating inputs
Input found: Midi Through:Midi Through Port-0 14:0
Input found: RtMidi Output Client:node-midi Virtual Output 128:0
Enumerating outputs
Output found: Midi Through:Midi Through Port-0 14:0
Output found: RtMidi Output Client:node-midi Virtual Output 128:0
Sending message
Sending message
Sending message
Sending message

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970586

Title:
  No sound support on Linux AWS kernel (but supported on GCP)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1970586/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970586] Re: No sound support on Linux AWS kernel (but supported on GCP)

[Pete Woods]

With input from our customer, I have created a very simple NPM project
to test out the sound / virtual MIDI support:

https://github.com/CircleCI-Public/midi-test

I'm getting the expected failures with it on the latest 22.04 AMI, so
I'll try the new kernel next.

$ node .
ALSA lib seq_hw.c:466:(snd_seq_hw_open) open /dev/snd/seq failed: No such file 
or directory

MidiOutAlsa::initialize: error creating ALSA sequencer client object.

ALSA lib seq_hw.c:466:(snd_seq_hw_open) open /dev/snd/seq failed: No
such file or directory

MidiInAlsa::initialize: error creating ALSA sequencer client object.

ALSA lib seq_hw.c:466:(snd_seq_hw_open) open /dev/snd/seq failed: No
such file or directory

MidiOutAlsa::initialize: error creating ALSA sequencer client object.

ALSA lib seq_hw.c:466:(snd_seq_hw_open) open /dev/snd/seq failed: No
such file or directory

MidiInAlsa::initialize: error creating ALSA sequencer client object.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970586

Title:
  No sound support on Linux AWS kernel (but supported on GCP)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1970586/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970586] Re: No sound support on Linux AWS kernel (but supported on GCP)

[Pete Woods]

I have asked the customer if they can provide a script so I get verify
if their virtual MIDI devices will work on this new kernel (rather than
guess at their needs).

I think they'll need at least:

CONFIG_SND_RAWMIDI=m

CONFIG_SND_SEQUENCER=m
CONFIG_SND_SEQ_DEVICE=m
CONFIG_SND_SEQ_DUMMY=m
CONFIG_SND_SEQ_HRTIMER_DEFAULT=y
CONFIG_SND_SEQ_MIDI=m
CONFIG_SND_SEQ_MIDI_EMUL=m
CONFIG_SND_SEQ_MIDI_EVENT=m
CONFIG_SND_SEQ_VIRMIDI=m

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970586

Title:
  No sound support on Linux AWS kernel (but supported on GCP)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1970586/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970586] Re: No sound support on Linux AWS kernel (but supported on GCP)

[Pete Woods]

Thankyou for doing this so quickly - let me see if I can get one of the
customers setup to work with this kernel.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970586

Title:
  No sound support on Linux AWS kernel (but supported on GCP)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1970586/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970586] Re: No sound support on Linux AWS kernel (but supported on GCP)

[Pete Woods]

** Description changed:

  In GCP images it is possible to create virtual MIDI devices and
  generally do stuff like audio routing, etc.
  
  At CircleCI, where we run many of our VMs on Ubuntu in GCP, several of
  our customers use this functionality to test audio equipment in their CI
  runs.
  
  Unfortunately they cannot run their tests on our AWS based VMs, as there
  is no sound support compiled into the kernel on the AWS kernel and
  images.
  
  See the package listings for the other kernels for, e.g. the loopback driver:
  ```
  linux-modules-extra-5.4.0-99-generic: 
/lib/modules/5.4.0-99-generic/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1031-oracle: 
/lib/modules/5.8.0-1031-oracle/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1032-gcp: 
/lib/modules/5.8.0-1032-gcp/kernel/sound/drivers/snd-aloop.ko
  ```
  
  We would love to be able to install the sound drivers (especially snd-
  aloop) with the linux-modules-extra-aws package, but currently cannot,
  and obviously do not want to start running our own kernels, as then we
  lose the immediacy of kernel patches provided upstream by Canonical.
  
  You can see the difference in the GCP:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/jammy/tree/debian.gcp/config/config.common.ubuntu#n6884
  
  and AWS kernel:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/tree/debian.aws/config/config.common.ubuntu
  
- again there. The reasoning for the removal appears to be in this commit:
+ again there. The reasoning for the removal appears to be in this commit from 
2016:
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/commit/debian.aws/config/config.common.ubuntu?id=b5e310c4cc872c3fc7c7dd09ce67efb11eeaf07c

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970586

Title:
  No sound support on Linux AWS kernel (but supported on GCP)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1970586/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970586] [NEW] No sound support on Linux AWS kernel (but supported on GCP)

[Pete Woods]

Public bug reported:

In GCP images it is possible to create virtual MIDI devices and
generally do stuff like audio routing, etc.

At CircleCI, where we run many of our VMs on Ubuntu in GCP, several of
our customers use this functionality to test audio equipment in their CI
runs.

Unfortunately they cannot run their tests on our AWS based VMs, as there
is no sound support compiled into the kernel on the AWS kernel and
images.

See the package listings for the other kernels for, e.g. the loopback driver:
```
linux-modules-extra-5.4.0-99-generic: 
/lib/modules/5.4.0-99-generic/kernel/sound/drivers/snd-aloop.ko
linux-modules-extra-5.8.0-1031-oracle: 
/lib/modules/5.8.0-1031-oracle/kernel/sound/drivers/snd-aloop.ko
linux-modules-extra-5.8.0-1032-gcp: 
/lib/modules/5.8.0-1032-gcp/kernel/sound/drivers/snd-aloop.ko
```

We would love to be able to install the sound drivers (especially snd-
aloop) with the linux-modules-extra-aws package, but currently cannot,
and obviously do not want to start running our own kernels, as then we
lose the immediacy of kernel patches provided upstream by Canonical.

You can see the difference in the GCP:
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/jammy/tree/debian.gcp/config/config.common.ubuntu#n6884

and AWS kernel:
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/tree/debian.aws/config/config.common.ubuntu

again there. The reasoning for the removal appears to be in this commit from 
2016:
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/commit/debian.aws/config/config.common.ubuntu?id=b5e310c4cc872c3fc7c7dd09ce67efb11eeaf07c

** Affects: linux-aws (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  In GCP images it is possible to create virtual MIDI devices and
  generally do stuff like audio routing, etc.
  
  At CircleCI, where we run many of our VMs on Ubuntu in GCP, several of
  our customers use this functionality to test audio equipment in their CI
  runs.
  
  Unfortunately they cannot run their tests on our AWS based VMs, as there
  is no sound support compiled into the kernel on the AWS kernel and
  images.
  
- See the package listings for, e.g. the loopback driver:
+ See the package listings for the other kernels for, e.g. the loopback driver:
  linux-modules-extra-5.4.0-99-generic: 
/lib/modules/5.4.0-99-generic/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1031-oracle: 
/lib/modules/5.8.0-1031-oracle/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1032-gcp: 
/lib/modules/5.8.0-1032-gcp/kernel/sound/drivers/snd-aloop.ko
  
  We would love to be able to install the sound drivers (especially snd-
  aloop) with the linux-modules-extra-aws package, but currently cannot,
  and obviously do not want to start running our own kernels, as then we
  lose the immediacy of kernel patches provided upstream by Canonical.

** Description changed:

  In GCP images it is possible to create virtual MIDI devices and
  generally do stuff like audio routing, etc.
  
  At CircleCI, where we run many of our VMs on Ubuntu in GCP, several of
  our customers use this functionality to test audio equipment in their CI
  runs.
  
  Unfortunately they cannot run their tests on our AWS based VMs, as there
  is no sound support compiled into the kernel on the AWS kernel and
  images.
  
  See the package listings for the other kernels for, e.g. the loopback driver:
  linux-modules-extra-5.4.0-99-generic: 
/lib/modules/5.4.0-99-generic/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1031-oracle: 
/lib/modules/5.8.0-1031-oracle/kernel/sound/drivers/snd-aloop.ko
  linux-modules-extra-5.8.0-1032-gcp: 
/lib/modules/5.8.0-1032-gcp/kernel/sound/drivers/snd-aloop.ko
  
  We would love to be able to install the sound drivers (especially snd-
  aloop) with the linux-modules-extra-aws package, but currently cannot,
  and obviously do not want to start running our own kernels, as then we
  lose the immediacy of kernel patches provided upstream by Canonical.
+ 
+ You can see the difference in the GCP:
+ 
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/jammy/tree/debian.gcp/config/config.common.ubuntu#n6884
+ 
+ and AWS kernel:
+ 
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/tree/debian.aws/config/config.common.ubuntu
+ 
+ again there. The reasoning for the removal appears to be in this commit:
+ 
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/commit/debian.aws/config/config.common.ubuntu?id=b5e310c4cc872c3fc7c7dd09ce67efb11eeaf07c

** Description changed:

  In GCP images it is possible to create virtual MIDI devices and
  generally do stuff like audio routing, etc.
  
  At CircleCI, where we run many of our VMs on Ubuntu in GCP, several of
  our customers use this functionality to test audio equipment in their CI
  runs.
  
  Unfortunately they 

[Bug 1964349] [NEW] package linux-firmware 1.187.27 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1

[Pete Jordan]

Public bug reported:

This is 16.04 updated to 20.04 with some Debian repositories glued on
(for a non-Snap Chromium); I've come to expect the odd issue, but still
reporting, in case.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-firmware 1.187.27
ProcVersionSignature: Ubuntu 5.4.0-97.110-generic 5.4.162
Uname: Linux 5.4.0-97-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  pete   1783 F pulseaudio
 /dev/snd/pcmC0D0p:   pete   1783 F...m pulseaudio
CasperMD5CheckResult: skip
Date: Wed Mar  9 13:15:55 2022
Dependencies:
 
ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
HibernationDevice: RESUME=UUID=25544052-705f-413e-8821-a612310589eb
InstallationDate: Installed on 2018-02-25 (1473 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: LENOVO 4291AB3
PackageArchitecture: all
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-97-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13
SourcePackage: initramfs-tools
Title: package linux-firmware 1.187.27 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/02/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET59WW (1.29 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4291AB3
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: LTL0011096
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr8DET59WW(1.29):bd04/02/2012:svnLENOVO:pn4291AB3:pvrThinkPadX220:rvnLENOVO:rn4291AB3:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X220
dmi.product.name: 4291AB3
dmi.product.version: ThinkPad X220
dmi.sys.vendor: LENOVO

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964349

Title:
  package linux-firmware 1.187.27 failed to install/upgrade: installed
  linux-firmware package post-installation script subprocess returned
  error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1964349/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1953199] Re: 0-byte files created in overlay filesystem

[Pete Woods]

So what we're saying here is that:

1. 
https://github.com/torvalds/linux/commit/@82a763e61e2b601309d696d4fa514c77d64ee1be
2. 
https://github.com/torvalds/linux/commit/@9b91b6b019fda817eb52f728eb9c79b3579760bc

need backporting to Ubuntu 18.04's 5.4 series Kernel?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953199

Title:
  0-byte files created in overlay filesystem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1953199/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1786202] Re: 18.04LTS ubuntu kernel load error rf kill switch status

[Pete]

All good thanks. I don't know what happened to fix it but it was a while
back. I'm on 20.04 now

Pete

On Thu, 1 Jul 2021, 10:17 Dan Streetman, <1786...@bugs.launchpad.net>
wrote:

> please reopen if this is still an issue
>
> ** Changed in: systemd (Ubuntu)
>Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1786202
>
> Title:
>   18.04LTS ubuntu kernel load error rf kill switch status
>
> Status in systemd package in Ubuntu:
>   Invalid
>
> Bug description:
>   I've just done the upgrade from 16.04LTS to 18.04LTS and the system
>   now hangs on boot. Booting to recovery mode shows it now hangs at the
>   "RF Kill Switch Status" step.
>
>   If I enter debug mode and the perform a full boot it seems to miss
>   this step and the boot completes
>
>   I didn't have this problem with 16.04 and my PC doesn't have wifi.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1786202/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786202

Title:
  18.04LTS ubuntu kernel load error rf kill switch status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1786202/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882432] Re: Can't open OpenArena on Xubuntu 20.04

[Ray Pete]

git repo build still crashes when I click fight, but that's more then I
could get before!!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882432

Title:
  Can't open OpenArena on Xubuntu 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openarena/+bug/1882432/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1909693] [NEW] package lxd (not installed) failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1

[Pete Ashdown]

Public bug reported:

do-release-upgrade on two separate 18.04.05 to 20.04.1 servers stall on
lxd install

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: lxd (not installed)
ProcVersionSignature: Ubuntu 4.15.0-128.131-generic 4.15.18
Uname: Linux 4.15.0-128-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Dec 30 14:58:50 2020
ErrorMessage: new lxd package pre-installation script subprocess returned error 
exit status 1
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.2
SourcePackage: lxd
Title: package lxd (not installed) failed to install/upgrade: new lxd package 
pre-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to focal on 2020-12-30 (0 days ago)

** Affects: lxd (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/1909693

Title:
  package lxd (not installed) failed to install/upgrade: new lxd package
  pre-installation script subprocess returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1909693/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1311403] Re: Can't type password after resume.

[Pete Cowley]

A workaround:

I turned the screen saver off in settings.
If IMANUALLY lock the screen when I restart it shows the standard login (not 
the screensaver login) and that works fine.

Hope this is helpful to those struggling with this.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311403

Title:
  Can't type password after resume.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1311403/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1311403] Re: Can't type password after resume.

[Pete Cowley]

I did not have this issue in 18.04 but now that I have upgraded to
20.04.01 (Ubuntu-studio) I now have it and it is really annoying.  I did
not know how to work around it so had to reboot my machine.  Fortunately
this thread has given me a couple of things to try now.

Interestingly, the login background had the xbuntu background showing
and the password box would not accept any text although it KNEW if the
caps lock key was pressed as it gave a warning.  The login screen was
completely different to the usual one after reboot.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311403

Title:
  Can't type password after resume.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1311403/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1805307] Re: Okular does not use system-wide printer settings

[Pete Wang]

I just switched from Xfce to KDE.  I'm experiencing the same problem
with Okular Version 1.9.3 on a new installation of Kubuntu 20.04.

In addition to what Bruce reported, I also tried changing the printer
setting from "Letter" to "Letter/ANSI A," but that made no difference.

I then tried printing the document with qpdfview 0.4.18, which worked as
expected (I'm noting this because I'm not sure if this is considered a
KDE application or not).  One thing I did differently than Bruce is that
I was printing duplex.

System Information:
KDE Plasma Version 5.18.5
KDE Frameworks Version 5.68.0
Qt Version 5.12.8
Kernel Version 5.8.0-9.3-liquorix-amd64

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805307

Title:
  Okular does not use system-wide printer settings

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/okular/+bug/1805307/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1880106] Re: colmap: error while loading shared libraries: libCGAL.so.13

[Pete Allen]

Really sorry, I compiled from source and accidentially overwrote my binary. 
I now cannot reproduce. Please close this.

Thank you for your time

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880106

Title:
  colmap: error while loading shared libraries: libCGAL.so.13

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/colmap/+bug/1880106/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1880106] [NEW] colmap: error while loading shared libraries: libCGAL.so.13

[Pete Allen]

Public bug reported:

Upgraded to 20.04, package colmap was working, but now when I try to
start it it gives colmap: error while loading shared libraries:
libCGAL.so.13: cannot open shared object file: No such file or directory

When I look for an installation candidate, I see cgal has gone to being
header only, so there isn't an library any more.

Description:Ubuntu 20.04 LTS
Release:20.04
X64


colmap:
  Installed: 3.6+dev2+git20191105-1build1
  Candidate: 3.6+dev2+git20191105-1build1
  Version table:
 *** 3.6+dev2+git20191105-1build1 500
500 http://gb.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
100 /var/lib/dpkg/status

** Affects: colmap (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/1880106

Title:
  colmap: error while loading shared libraries: libCGAL.so.13

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/colmap/+bug/1880106/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1873295] [NEW] Updated 04-16-2000 and system-monitor shell extension broke

[Pete Graner]

Public bug reported:

I updated my 20.04 beta box to on 16 Apr 2020 and the system-monitor
applet stopped working. Going to
https://extensions.gnome.org/extension/120/system-monitor/ shows error.
I removed and tried readding with same result. When adding back the
/var/log/syslog shows:

Apr 16 11:07:58 x1 gnome-shell[1892]: [System monitor] applet init from 
/home/pgraner/.local/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com
Apr 16 11:07:58 x1 gnome-shell[1892]: [System monitor] applet enabling
Apr 16 11:07:58 x1 gnome-shell[1892]: JS ERROR: Extension 
system-moni...@paradoxxx.zero.gmail.com: Error: Tried to construct an object 
without a GType; are you using GObject.registerClass() when inheriting from a 
GObject 
type?#012SystemMonitor_TipItem@/home/pgraner/.local/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:640:9#012tip_format@/home/pgraner/.local/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:898:27#012SystemMonitor_Cpu@/home/pgraner/.local/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:1196:14#012createCpus@/home/pgraner/.local/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:1363:20#012enable@/home/pgraner/.local/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:2316:26#012_callExtensionEnable@resource:///org/gnome/shell/ui/extensionSystem.js:166:32#012loadExtension@resource:///org/gnome/shell/ui/extensionSystem.js:336:26#012callback@resource:///org/gnome/shell/ui/extensionDownloader.js:232:39#012gotExtensionZipFile/<@resource:///org/gnome/shell/ui/extensionDownloader.js:115:13
Apr 16 11:08:00 x1 gnome-shell[1892]: JS ERROR: TypeError: this.tip_labels[i] 
is 
undefined#012update@/home/pgraner/.local/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:925:56

Nothing I've done can get it working. Googleing hasn't revealed anything
useful.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.1-5ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
Uname: Linux 5.4.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 16 11:11:22 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-01-25 (82 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
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/1873295

Title:
  Updated 04-16-2000 and system-monitor shell extension broke

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873295/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1867803] Re: ALSA: No soundcards found after updating kernel to 5.3.0.42.36

[Pete Gamache]

I concur, -46 fixed the issue on my X1C 7th gen. Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867803

Title:
  ALSA: No soundcards found after updating kernel to 5.3.0.42.36

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867803/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1868165] Re: [X1 Carbon 7th ed] 5.3.0-42 loses internal audio; regression from 5.3.0-40

[Pete Gamache]

*** This bug is a duplicate of bug 1867803 ***
https://bugs.launchpad.net/bugs/1867803

This issue is still broken with -43 and -45 kernels.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868165

Title:
  [X1 Carbon 7th ed] 5.3.0-42 loses internal audio; regression from
  5.3.0-40

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868165/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1868165] [NEW] [X1 Carbon 7th ed] 5.3.0-42 loses internal audio; regression from 5.3.0-40

[Pete Gamache]

Public bug reported:

I have a Lenovo ThinkPad X1 Carbon 7th edition laptop running Ubuntu
19.10 desktop. I recently applied a software update that contained a new
kernel, 5.3.0-42, and upon restarting, the internal audio interface was
not found; internal speakers and the headphone output were unusable.

Upon rebooting with the previous kernel, 5.3.0-40, the problem went away
again. Subsequent testing confirms this is repeatable.

Some relevant lines from `dmesg` follow.

On kernel 5.3.0-40 (working):

[4.386007] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[4.391825] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[4.392016] thermal thermal_zone5: failed to read out thermal zone (-61)
[4.430083] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC285: 
line_outs=2 (0x14/0x17/0x0/0x0/0x0) type:speaker
[4.430085] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[4.430087] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
[4.430087] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[4.430088] snd_hda_codec_realtek hdaudioC0D0:inputs:
[4.430089] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x19


On kernel 5.3.0-42 (broken):

[3.076809] i915 :00:02.0: fb0: i915drmfb frame buffer device
[3.088029] snd_soc_skl :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[3.173463] snd_soc_skl :00:1f.3: Direct firmware load for 
9dc8-LENOVO-TP-N2H-4752-tplg.bin failed with error -2
[3.173465] snd_soc_skl :00:1f.3: tplg fw 
9dc8-LENOVO-TP-N2H-4752-tplg.bin load failed with -2, falling back to 
dfw_sst.bin
[3.173480] snd_soc_skl :00:1f.3: Direct firmware load for dfw_sst.bin 
failed with error -2
[3.173481] snd_soc_skl :00:1f.3: Fallback tplg fw dfw_sst.bin load 
failed with -2
[3.173484] snd_soc_skl :00:1f.3: Failed to init topology!
[3.173486] snd_soc_skl :00:1f.3: ASoC: failed to probe component -2
[3.173496] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: failed to 
instantiate card -2
[3.173508] skl_hda_dsp_generic: probe of skl_hda_dsp_generic failed with 
error -2


I've attached `lspci -vnvn` and `dmesg` output for both the -40 and -42 kernels.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-40-generic 5.3.0-40.32
ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gamache1768 F pulseaudio
 /dev/snd/controlC1:  gamache1768 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 19 15:08:14 2020
InstallationDate: Installed on 2019-11-21 (119 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: LENOVO 20QD0007US
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=90290cff-6557-4384-b8a9-1b83f860ea01 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-40-generic N/A
 linux-backports-modules-5.3.0-40-generic  N/A
 linux-firmware1.183.4
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/21/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET46W (1.29 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QD0007US
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET46W(1.29):bd02/21/2020:svnLENOVO:pn20QD0007US:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD0007US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QD0007US
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug eoan

** Attachment added: "Contains `lspci -vnvn` and `dmesg` output for the 
5.3.0-40 and -42 kernels."
   
https://bugs.launchpad.net/bugs/1868165/+attachment/5339013/+files/gamache-bug-materials.tgz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868165

Title:
  [X1 Carbon 7th ed] 5.3.0-42 loses internal audio; regression from
  5.3.0-40

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868165/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1864237] [NEW] Clicked settings->configure kontact and program crashes

[pete]

Public bug reported:

A fresh install of Kubuntu 20.04 trying to setup kontact when I click
settings->configure kontact the app crashes.

I would expect this to open the settings window.

This happens every time have rebooted and tried again.

lsb_release -rd ->

Description:Ubuntu Focal Fossa (development branch)
Release:20.04

apt-cache policy ->

  Installed: 4:19.04.3-0ubuntu1
  Candidate: 4:19.04.3-0ubuntu1
  Version table:
 *** 4:19.04.3-0ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: kontact 4:19.04.3-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CurrentDesktop: KDE
Date: Fri Feb 21 19:39:39 2020
InstallationDate: Installed on 2020-02-21 (0 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200221)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: kontact
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: kontact (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/1864237

Title:
  Clicked settings->configure kontact and program crashes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kontact/+bug/1864237/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1861940] [NEW] gimp crashed while editing an image

[Pete Hall]

Public bug reported:

```
GNU Image Manipulation Program version 2.10.14
git-describe: GIMP_2_10_12-511-ga4f55d6c7e
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
9.2.1-9ubuntu2' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs 
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-9 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib 
--with-target-system-zlib=auto --enable-multiarch --disable-werror 
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 
--enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none,hsa 
--without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu 
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) 

using babl version 0.1.72 (compiled against version 0.1.72)
using GEGL version 0.4.18 (compiled against version 0.4.18)
using GLib version 2.62.1 (compiled against version 2.62.1)
using GdkPixbuf version 2.40.0 (compiled against version 2.40.0)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.42.3 (compiled against version 1.42.3)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)

```
> fatal error: Aborted

Stack trace:
```

# Stack traces obtained from PID 6744 - Thread 6744 #

[New LWP 6746]
[New LWP 6747]
[New LWP 6748]
[New LWP 6749]
[New LWP 6822]
[New LWP 6994]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__libc_read (nbytes=256, buf=0x7fff9d5c3550, fd=52) at 
../sysdeps/unix/sysv/linux/read.c:26
  Id   Target Id  Frame 
* 1Thread 0x7f24aeb54500 (LWP 6744) "gimp-2.10"   __libc_read (nbytes=256, 
buf=0x7fff9d5c3550, fd=52) at ../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x7f24ae38e700 (LWP 6746) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7f24ad5b9700 (LWP 6747) "gmain"   0x7f24afb20c2f in 
__GI___poll (fds=0x564cac691f50, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  4Thread 0x7f24acdb8700 (LWP 6748) "gdbus"   0x7f24afb20c2f in 
__GI___poll (fds=0x564cac80ee00, nfds=3, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  5Thread 0x7f249660e700 (LWP 6749) "async"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  6Thread 0x7f249552c700 (LWP 6822) "swap writer" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  7Thread 0x7f23c8c54700 (LWP 6994) "paint"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38

Thread 7 (Thread 0x7f23c8c54700 (LWP 6994)):
#0  0x7f24afb2694d in syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7f24afe13d83 in g_cond_wait () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x564cabb6d32d in  ()
#3  0x7f24afdf in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f24afc07669 in start_thread (arg=) at 
pthread_create.c:479
ret = 
pd = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139791668954880, 
210471390955828466, 140735833453854, 140735833453855, 140735833454000, 
139791668951296, -239764903826688782, -242383913082686222}, mask_was_saved = 
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, 
canceltype = 0}}}
not_first_call = 0
#5  0x7f24afb2d323 in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 6 (Thread 0x7f249552c700 (LWP 6822)):
#0  0x7f24afb2694d in syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7f24afe13d83 in g_cond_wait () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f24b02dcc4d in  () at /usr/lib/x86_64-linux-gnu/libgegl-0.4.so.0
#3  0x7f24afdf in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f24afc07669 in start_thread (arg=) at 
pthread_create.c:479
ret = 
pd = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139795100780288, 
210471390955828466, 140735833449198, 140735833449199, 140735833449344, 
139795100776704, -242468461185469198, -242383913082686222}, mask_was_saved = 
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = 

[Bug 1858092] Re: Network Manager not saving OpenVPN password

[Pete]

Tested with network-manager 1.20.4-2ubuntu2.2 from proposed on eoan.

Result: VPN passwords are saved correctly again!

Thank you so much! I built a vpn benchmark script that relies on the password 
being able to be saved. It uses the nmcli tool to add new connections and set 
the password. 
It  can now run again. 

** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858092

Title:
  Network Manager not saving OpenVPN password

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1858092/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1858092] Re: Network Manager not saving OpenVPN password

[Pete]

Is there a rough timeline when this will be available in eoan?

I can confirm the bug on all my ubuntu 19.10 installs and I have to
switch vpns frequently.

Thanks for the great work!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858092

Title:
  Network Manager not saving OpenVPN password

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1858092/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1857563] [NEW] Kubuntu Installation does not allow to set password for Encrypted Volume

[Pete]

Public bug reported:

Installing Kubuntu allows to partition the system manually choosing "Manual" in 
the disk setup dialog. 
There you can add a new partition. When choosing the type "Volume for 
Encryption", nothing really happens. Normally the installer should ask for the 
password for the encrypted volume and then mount it, so it can be used as 
installation target. Instead it just shows as a crypto partition but the user 
cannot do anything with it. 

Steps to reproduce:
 - Use Kubuntu 19.10 installer on usb stick
 - in disk setup choose manual (for manual partitioning)
 - create a new partition with type "Volume for Encryption"
 - What happens: Volume is created but user cannot set password or configure 
the volume's mount point
 - Expected: Here you should somehow be able to enter the volume password for 
the new volume, then it should be mounted and then you can change the mount 
point for the installation

Importance: this does block a user from using the ui installer to setup
an encrypted dual boot.

Workaround: use ubuntu installer to setup encrypted system and then
install kubuntu-desktop

PS: Not sure if this is the right place to report

** Affects: kde-workspace (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

- Installing Kubuntu during disk setup choosing the manual setup does
- allow to set the partition "Volume for Encryption".
+ Installing Kubuntu allows to partition the system manually choosing "Manual" 
in the disk setup dialog. 
+ There you can add a new partition. When choosing the type "Volume for 
Encryption", nothing really happens. Normally the installer should ask for the 
password for the encrypted volume and then mount it, so it can be used as 
installation target. Instead it just shows as a crypto partition but the user 
cannot do anything with it. 
  
- Normally the installer should ask for the password for the encrypted
- volume and then mount it, so it can be used as installation target.
- 
- Steps to reproduce: 
-  - Use Kubuntu 19.10 installer on usb stick
-  - in disk setup choose manual (for manual partitioning)
-  - create a new partition with type "Volume for Encryption"
-  - What happens: Volume is created but user cannot set password or configure 
the volume's mount point
-  - Expected: Here you should somehow be able to enter the volume password for 
the new volume, then it should be mounted and then you can change the mount 
point for the installation
+ Steps to reproduce:
+  - Use Kubuntu 19.10 installer on usb stick
+  - in disk setup choose manual (for manual partitioning)
+  - create a new partition with type "Volume for Encryption"
+  - What happens: Volume is created but user cannot set password or configure 
the volume's mount point
+  - Expected: Here you should somehow be able to enter the volume password for 
the new volume, then it should be mounted and then you can change the mount 
point for the installation
  
  Importance: this does block a user from using the ui installer to setup
  an encrypted dual boot.
  
  Workaround: use ubuntu installer to setup encrypted system and then
  install kubuntu-desktop
  
- 
  PS: Not sure if this is the right place to report

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857563

Title:
  Kubuntu Installation does not allow to set password for Encrypted
  Volume

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1857563/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices

[Pete Heist]

*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790

I just wanted to report that USB is working for me with the
5.3.0-1014-raspi2 aarch64 kernel, but neither the keyboard not the mouse
works at boot time when I have my mouse (a Microsoft Basic Optical Mouse
v2.0) plugged in via my Apple USB keyboard's built-in USB hub.

I must disconnect the mouse from the keyboard and plug it straight into
an open USB port on the Pi. Afterwards, I can then plug it back into the
keyboard, and the keyboard and mouse both work fine until reboot.

That was confusing me into thinking that I was seeing this issue, when
it's probably a little different. I don't have another hub to test to
see if the same happens with all USB hubs.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848703

Title:
  Raspberry Pi 4 - USB Bus not detecting any devices

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1758243] Re: bumblebee needs configuration changes to work with nvidia-driver-390 and libglvnd0

[Pete Vander Giessen]

A followup to the above (#36):

I think that my kernel might be switching the card on and off
successfully, w/out the use of bbswitch. If I `optirun glxgears`, I can
see the card being used via nvidia-smi (and via a sensors plugin I've
got running in gnome). When I close the process, nvidia-smi reports the
card as off.

In short: the above instructions worked for me, after turning bbswitch
off, due to the 5.0 kernel recognizing my MX150 and switching it on/off
as appropriate.

That's pretty darn cool!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758243

Title:
  bumblebee needs configuration changes to work with nvidia-driver-390
  and libglvnd0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/1758243/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1758243] Re: bumblebee needs configuration changes to work with nvidia-driver-390 and libglvnd0

[Pete Vander Giessen]

I had all this working wonderfully on a Thinkpad T480 on Ubuntu Disco,
until a recent reboot after an update (possibly due to kernel 5.0.0-27,
possibly due to a udev update)

bbswitch would fail to enable the card, with the following in dmesg:

pci :00:01.0: Refused to change power state, currently in D3

After a lot of futzing about and installing/reinstalling, the steps
mentioned in the OP, #31, #32 and #35 worked, with the following change
to bumblebee.conf:

PMMethod=none

I think that this means that my nvidia card is on all the time -- I'm
not sure how to check its state with bbswitch disabled -- but I can at
least run the desktop off of the Intel card, and games and such off of
the nvidia card, which helps with stability and heat for me.

(It's possible that I did something to change the acpi power management
settings when booting the kernel, and those changes got blown up by the
update.)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758243

Title:
  bumblebee needs configuration changes to work with nvidia-driver-390
  and libglvnd0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/1758243/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1842207] [NEW] Ubiquity crash on minimal install

[Pete Misik]

Public bug reported:

Attempted to do a minimal install of 18.04.3 on a Latitude e6420 core i5
8GB RAM 120GB Intel SSD.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.12
ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep  1 07:14:40 2019
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubiquity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic ubiquity-18.04.14.12 ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842207

Title:
  Ubiquity crash on minimal install

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1842207/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1840732] Re: Upgrade 18.04 LTS to 19.10 fail and rollback

[Pete]

Thanks, no worries. I had run ppa-purge but it requires the name of the 
package.
I'll have a look in .. 'main.log' and 'apt.log' and see if anything 
jumps out.
Probably .. what's that thing to run dota .. vulkan!

Cheers


On 2019/08/20 07:31, Chris Guiver wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better.
>
> The error message says " This was likely caused by:   * Unofficial
> software packages not provided by Ubuntu. Please use the tool 'ppa-
> purge' from the ppa-purge package to remove software from a Launchpad
> PPA and try the upgrade again."
>
> I can see packages in the listing that aren't from Ubuntu repositories,
> plus many PPAs where they could have come from. The error message you
> received fits, and the fix is `ppa-purge` i believe as the error message
> states. As such I've marked this bug invalid.  If you believe i'm in
> error, please return status to 'New' and leave a message as to why you
> believe I'm in error.
>
> The fix is to remove your added 3rd party packages, then try the upgrade
> process again.  If you need help removing these packages, I'd recommend
> looking at https://discourse.ubuntu.com/t/community-support/709 for
> possibly support options.
>
> Thanks again for trying to help us make Ubuntu better.
>
> ** Changed in: ubuntu-release-upgrader (Ubuntu)
> Status: New => Invalid
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840732

Title:
  Upgrade 18.04 LTS to 19.10 fail and rollback

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1840732/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1840732] [NEW] Upgrade 18.04 LTS to 19.10 fail and rollback

[Pete]

Public bug reported:

Could not calculate the upgrade

An unresolvable problem occurred while calculating the upgrade.

 This was likely caused by:
 * Unofficial software packages not provided by Ubuntu. Please use the tool 
'ppa-purge' from the ppa-purge package to remove software from a Launchpad PPA 
and try the upgrade again.

If none of this applies, then please report this bug using the command
'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to
investigate this yourself the log files in '/var/log/dist-upgrade' will
contain details about the upgrade. Specifically, look at 'main.log' and
'apt.log'.

-
Apologies, I don't know what package is bugging out, I think I'll just stay on 
18.04.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.34
ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
Uname: Linux 4.15.0-58-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug 20 06:48:30 2019
InstallationDate: Installed on 2019-04-30 (111 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_ZA.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to bionic on 2019-08-20 (0 days ago)
VarLogDistupgradeTermlog:
 
mtime.conffile..etc.update-manager.release-upgrades: 2019-06-21T20:39:29.262820

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840732

Title:
  Upgrade 18.04 LTS to 19.10 fail and rollback

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1840732/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1835604] Re: usbmuxd: libssl.so.1.0.0: cannot open shared object file

[Pete]

** Tags added: disco

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835604

Title:
  usbmuxd: libssl.so.1.0.0: cannot open shared object file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usbmuxd/+bug/1835604/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1835605] Re: /usr/lib/gvfs/gvfs-afc-volume-monitor: error while loading shared libraries: libssl.so.1.0.0

[Pete]

** Package changed: ubuntu => gvfs (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835605

Title:
  /usr/lib/gvfs/gvfs-afc-volume-monitor: error while loading shared
  libraries: libssl.so.1.0.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1835605/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1835605] [NEW] /usr/lib/gvfs/gvfs-afc-volume-monitor: error while loading shared libraries: libssl.so.1.0.0

[Pete]

Public bug reported:

When I upgraded to Disco, I got the following error:

gvfs-afc-volume-monitor[6816]: /usr/lib/gvfs/gvfs-afc-volume-monitor:
error while loading shared libraries: libssl.so.1.0.0: cannot open
shared object file: No such file or directory

dpkg --list gvfs**
Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten
| Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/
 Halb installiert/Trigger erWartet/Trigger anhängig
|/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: GROSS=schlecht)
||/ NameVersion  Architektur  Beschreibung
+++-===---
ii  gvfs:amd64  1.40.1-1 amd64userspace virtual filesystem - 
GIO module
ii  gvfs-backends   1.40.1-1 amd64userspace virtual filesystem - 
backends
ii  gvfs-bin1.40.1-1 amd64userspace virtual filesystem - 
deprecated command-line tools
ii  gvfs-common 1.40.1-1 all  userspace virtual filesystem - 
common data files
ii  gvfs-daemons1.40.1-1 amd64userspace virtual filesystem - 
servers
ii  gvfs-fuse   1.40.1-1 amd64userspace virtual filesystem - 
fuse server
ii  gvfs-libs:amd64 1.40.1-1 amd64userspace virtual filesystem - 
private libraries


ldd -r /usr/lib/gvfs/gvfs-afc-volume-monitor
linux-vdso.so.1 (0x7ffcd31f7000)
libglib-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 
(0x7fb3eb9bb000)
libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 
(0x7fb3eb95f000)
libimobiledevice.so.6 => /usr/local/lib/libimobiledevice.so.6 
(0x7fb3eb73c000)
libplist.so.3 => /usr/local/lib/libplist.so.3 (0x7fb3eb52d000)
libgio-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 
(0x7fb3eb364000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fb3eb179000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7fb3eb103000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fb3eb0e2000)
libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 
(0x7fb3eb0d8000)
libssl.so.1.0.0 => not found
libcrypto.so.1.0.0 => not found
libusbmuxd.so.4 => /usr/local/lib/libusbmuxd.so.4 (0x7fb3eaed)
libgmodule-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 
(0x7fb3eaec8000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fb3eaeac000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fb3eaea6000)
libmount.so.1 => /lib/x86_64-linux-gnu/libmount.so.1 
(0x7fb3eae4a000)
libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 
(0x7fb3eae2)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7fb3eae05000)
/lib64/ld-linux-x86-64.so.2 (0x7fb3ebb27000)
libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1 
(0x7fb3eadae000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fb3eada3000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7fb3ead9a000)
undefined symbol: ERR_remove_thread_state, version OPENSSL_1.0.0
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: SSL_CTX_use_RSAPrivateKey, version OPENSSL_1.0.0  
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: CRYPTO_cleanup_all_ex_data, version OPENSSL_1.0.0 
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: EVP_PKEY_free, version OPENSSL_1.0.0  
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: PEM_write_bio_X509, version OPENSSL_1.0.0 
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: X509_set_notAfter, version OPENSSL_1.0.0  
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: ASN1_INTEGER_set, version OPENSSL_1.0.0   
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: X509_set_notBefore, version OPENSSL_1.0.0 
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: RSA_new, version OPENSSL_1.0.0
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: BIO_s_mem, version OPENSSL_1.0.0  
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: RSA_free, version OPENSSL_1.0.0   
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: SSL_set_bio, version OPENSSL_1.0.0
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: SSL_COMP_get_compression_methods, version OPENSSL_1.0.0   
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: SSL_read, version OPENSSL_1.0.0   
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: X509V3_EXT_conf_nid, version OPENSSL_1.0.0
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: BN_new, version OPENSSL_1.0.0 
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: CRYPTO_set_id_callback, version OPENSSL_1.0.0 
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: BIO_new_mem_buf, version OPENSSL_1.0.0   

[Bug 1835604] [NEW] usbmuxd: libssl.so.1.0.0: cannot open shared object file

[Pete]

Public bug reported:

After upgrading from xenial to disco, I got the follwing error:

/usr/local/sbin/usbmuxd: error while loading shared libraries:
libssl.so.1.0.0: cannot open shared object file: No such file or
directory

ldd -r /usr/local/sbin/usbmuxd
linux-vdso.so.1 (0x7fffa2f8a000)
libusb-1.0.so.0 => /lib/x86_64-linux-gnu/libusb-1.0.so.0 
(0x7f00e2d7a000)
libimobiledevice.so.6 => /usr/local/lib/libimobiledevice.so.6 
(0x7f00e2b57000)
libplist.so.3 => /usr/local/lib/libplist.so.3 (0x7f00e2948000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f00e2927000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f00e273c000)
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x7f00e2716000)
libssl.so.1.0.0 => not found
libcrypto.so.1.0.0 => not found
libusbmuxd.so.4 => /usr/local/lib/libusbmuxd.so.4 (0x7f00e250c000)
/lib64/ld-linux-x86-64.so.2 (0x7f00e31d4000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f00e2501000)
undefined symbol: ERR_remove_thread_state, version OPENSSL_1.0.0
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: SSL_CTX_use_RSAPrivateKey, version OPENSSL_1.0.0  
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: CRYPTO_cleanup_all_ex_data, version OPENSSL_1.0.0 
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: EVP_PKEY_free, version OPENSSL_1.0.0  
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: PEM_write_bio_X509, version OPENSSL_1.0.0 
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: X509_set_notAfter, version OPENSSL_1.0.0  
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: ASN1_INTEGER_set, version OPENSSL_1.0.0   
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: X509_set_notBefore, version OPENSSL_1.0.0 
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: RSA_new, version OPENSSL_1.0.0
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: BIO_s_mem, version OPENSSL_1.0.0  
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: RSA_free, version OPENSSL_1.0.0   
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: SSL_set_bio, version OPENSSL_1.0.0
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: SSL_COMP_get_compression_methods, version OPENSSL_1.0.0   
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: SSL_read, version OPENSSL_1.0.0   
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: X509V3_EXT_conf_nid, version OPENSSL_1.0.0
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: BN_new, version OPENSSL_1.0.0 
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: CRYPTO_set_id_callback, version OPENSSL_1.0.0 
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: BIO_new_mem_buf, version OPENSSL_1.0.0
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: SSL_write, version OPENSSL_1.0.0  
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: SSL_shutdown, version OPENSSL_1.0.0   
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: X509V3_EXT_cleanup, version OPENSSL_1.0.0 
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: ASN1_TIME_free, version OPENSSL_1.0.0 
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: EVP_cleanup, version OPENSSL_1.0.0
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: BIO_s_socket, version OPENSSL_1.0.0   
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: EVP_PKEY_assign, version OPENSSL_1.0.0
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: SSL_set_verify, version OPENSSL_1.0.0 
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: PEM_read_bio_X509, version OPENSSL_1.0.0  
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: X509_free, version OPENSSL_1.0.0  
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: SSL_set_connect_state, version OPENSSL_1.0.0  
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: X509_EXTENSION_free, version OPENSSL_1.0.0
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: SSL_do_handshake, version OPENSSL_1.0.0   
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: TLSv1_method, version OPENSSL_1.0.0   
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: SSL_CTX_free, version OPENSSL_1.0.0   
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: X509_set_serialNumber, version OPENSSL_1.0.0  
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: SSL_new, version OPENSSL_1.0.0
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: X509_sign, version OPENSSL_1.0.0  
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: EVP_sha1, version OPENSSL_1.0.0   
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: X509V3_set_ctx, version OPENSSL_1.0.0 
(/usr/local/lib/libimobiledevice.so.6)
undefined symbol: BN_free, version OPENSSL_1.0.0

[Bug 1832766] Re: LDAP group_members_are_ids = false fails in Rocky/Stein

[Pete Vander Giessen]

Reading through the code, and testing a few hacks on _dn_to_id, I can
confirm that the method naively finds the value of the first element of
the user key, without trying to figure out whether it's a uid or not.

@afreiberger one thing I'm not clear on -- in your case, is there a
"uid" field in the key that you're passing in. Is it just a matter of
finding and returning that uid? Or do you want to actually do a lookup
for "Name.domain.tld" in a database, and return the uid of that entry?

** Changed in: keystone (Ubuntu)
 Assignee: James Page (james-page) => Pete Vander Giessen (petevg)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832766

Title:
  LDAP group_members_are_ids = false fails in Rocky/Stein

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1832766/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825843] Re: systemd issues with bionic-rocky causing nagios alert and can't restart daemon

[Pete Vander Giessen]

After IRC conversations and more testing, I think that I have a clean
reproduction of this bug, along with a root cause.

The root cause: the charm takes control of the radosgw service, and
changes the name, but doesn't remove the old nrpe check.

To reproduce:

1) juju deploy the following bundle: https://paste.ubuntu.com/p/wpVt447Vwz/
2) juju ssh into ceph-radosgw/0 and note that there is a "check_radosgw.cfg" in 
/etc/nagios/nrpe.d.
3) Trigger the config-changed hooked on the ceph-radosgw charm. You might 
change the number of ceph replicas, for example.
4) Note that there is now a "check_ceph-radosgw@.cfg" check, in 
addition to the check_radosgw.cfg check.
5) Run both checks (cat the files to get the command). Note that the new, 
hostname based check succeeds, but the old check does not.

The original check will also fail if you run it during step 2,
suggesting that the service has been changed, but the nagios monitoring
is not updated until the config-changed hook runs.

This bug can be closed once the charm places checks in
/etc/nagios/nrpe.d that accurately reflect the running services, and
cleans up outdated checks 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/1825843

Title:
  systemd issues with bionic-rocky causing nagios alert and can't
  restart daemon

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ceph-radosgw/+bug/1825843/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825843] Re: systemd issues with bionic-rocky causing nagios alert and can't restart daemon

[Pete Vander Giessen]

After further reading of code and testing, I think that I am completely
wrong about what is or is not broken. radosgw is inactive, but that's
deliberate. The charm has created a new service called "ceph-
radosgw@rgw...", along with a service to keep track of it called ceph-
radosgw.target. Those seem to be running just fine.

https://paste.ubuntu.com/p/szvhrRT9PM/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825843

Title:
  systemd issues with bionic-rocky causing nagios alert and can't
  restart daemon

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ceph-radosgw/+bug/1825843/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825843] Re: systemd issues with bionic-rocky causing nagios alert and can't restart daemon

[Pete Vander Giessen]

I can verify that this happens with the minimal bionic-rocky bundle
found in the ceph-radosgw charm's tests.

It's a bit tricky to spot at first, though, as the workload status is
green.

Filed a separate bug about that: https://bugs.launchpad.net/charm-ceph-
radosgw/+bug/1825884

** Changed in: charm-ceph-radosgw
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825843

Title:
  systemd issues with bionic-rocky causing nagios alert and can't
  restart daemon

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ceph-radosgw/+bug/1825843/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1380380] Re: free(1) translated output columns misaligned/translation bug

[Pete]

The problem exists still (and now for a few years), is there any hope
it'll be fixed in the future?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1380380

Title:
  free(1) translated output columns misaligned/translation bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1380380/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1801494] Re: dock missing

[Pete Forsyth]

I had this problem with a fresh install of Ubuntu Mate 18.10 on a 2008
white Macbook, 2.4 GHz. dual-booting with MacOS 10.6.8, using rEFInd. I
have never seen the menu bar of Ubuntu Mate on this install, it was
absent on the first boot.

I've tried many of the solutions suggested here and in other threads, to
no avail. I was able to sort of "fix" it by switching from gdm to
lightdm, which gives me a minimal but functional window manager,
allowing me (among other things) to connect to a WiFi network.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801494

Title:
  dock missing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1801494/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818352] [NEW] systemd-u+ running CPU at 99-100%

[Pete]

Public bug reported:

I upgraded to 18.10 and afterwards the fan was running constantly at
high speed.  I looked it up and found a post where the user had a
similar problem, and the reply was to run top, so I did and systemd-u+
was using 99-100% CPU, causing the overheating. I turned it off using
the second answer here: https://askubuntu.com/questions/907246/how-to-
disable-systemd-resolved-in-ubuntu and it has gone away.

I edited etc/systemd/resolved.conf as the guy said, and just put my hub
ip in as the DNS and the internet works fine.

uname --all says: Linux 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11
15:13:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: systemd ubuntu18.10

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818352

Title:
  systemd-u+ running CPU at 99-100%

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1818352/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1817228] Re: pip install scrapy and python -m pip install scrapy cause seg fault

[Pete]

I ran it with valgrind and turned binaries off for pip:

valgrind --log-file="scrapy-valgrind" --leak-check=yes pip install --no-
binary :all: --global-option build --global-option --debug scrapy

and it worked!

So this should work as well:

pip install  --no-binary :all:

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817228

Title:
  pip install scrapy and python -m pip install scrapy cause seg fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1817228/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1817228] Re: pip install scrapy and python -m pip install scrapy cause seg fault

[Pete]

ran it with strace, last few lines are:

rmdir("/tmp/pip-build-_sXoIB/incremental") = 0
lstat("/tmp/pip-build-_sXoIB/pyOpenSSL", {st_mode=S_IFDIR|0755, st_size=4096, 
...}) = 0
lstat("/tmp/pip-build-_sXoIB/pyOpenSSL", {st_mode=S_IFDIR|0755, st_size=4096, 
...}) = 0
openat(AT_FDCWD, "/tmp/pip-build-_sXoIB/pyOpenSSL", 
O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = 4
fstat(4, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
getdents(4, /* 4 entries */, 32768) = 128
getdents(4, /* 0 entries */, 32768) = 0
close(4)= 0
lstat("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL", {st_mode=S_IFDIR|0755, 
st_size=4096, ...}) = 0
lstat("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL", {st_mode=S_IFDIR|0755, 
st_size=4096, ...}) = 0
openat(AT_FDCWD, "/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL", 
O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = 4
fstat(4, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
getdents(4, /* 18 entries */, 32768)= 560
getdents(4, /* 0 entries */, 32768) = 0
close(4)= 0
lstat("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL/tsafe.py", 
{st_mode=S_IFREG|0644, st_size=1102, ...}) = 0
unlink("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL/tsafe.py") = 0
lstat("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL/__init__.pyc", 
{st_mode=S_IFREG|0644, st_size=643, ...}) = 0
unlink("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL/__init__.pyc") = 0
lstat("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL/rand.py", {st_mode=S_IFREG|0644, 
st_size=1042, ...}) = 0
unlink("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL/rand.py") = 0
lstat("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL/_util.pyc", 
{st_mode=S_IFREG|0644, st_size=4979, ...}) = 0
unlink("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL/_util.pyc") = 0
lstat("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL/debug.py", 
{st_mode=S_IFREG|0644, st_size=1049, ...}) = 0
unlink("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL/debug.py") = 0
lstat("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL/__init__.py", 
{st_mode=S_IFREG|0644, st_size=447, ...}) = 0
unlink("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL/__init__.py") = 0
lstat("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL/tsafe.pyc", 
{st_mode=S_IFREG|0644, st_size=1745, ...}) = 0
unlink("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL/tsafe.pyc") = 0
lstat("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL/crypto.pyc", 
{st_mode=S_IFREG|0644, st_size=103974, ...}) = 0
unlink("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL/crypto.pyc") = 0
lstat("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL/_util.py", 
{st_mode=S_IFREG|0644, st_size=4174, ...}) = 0
unlink("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL/_util.py") = 0
lstat("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL/rand.pyc", 
{st_mode=S_IFREG|0644, st_size=1460, ...}) = 0
unlink("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL/rand.pyc") = 0
lstat("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL/version.pyc", 
{st_mode=S_IFREG|0644, st_size=734, ...}) = 0
unlink("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL/version.pyc") = 0
lstat("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL/version.py", 
{st_mode=S_IFREG|0644, st_size=626, ...}) = 0
unlink("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL/version.py") = 0
lstat("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL/debug.pyc", 
{st_mode=S_IFREG|0644, st_size=1366, ...}) = 0
unlink("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL/debug.pyc") = 0
lstat("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL/SSL.pyc", {st_mode=S_IFREG|0644, 
st_size=87510, ...}) = 0
unlink("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL/SSL.pyc") = 0
lstat("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL/SSL.py", {st_mode=S_IFREG|0644, 
st_size=88967, ...}) = 0
unlink("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL/SSL.py") = 0
lstat("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL/crypto.py", 
{st_mode=S_IFREG|0644, st_size=100500, ...}) = 0
unlink("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL/crypto.py") = 0
rmdir("/tmp/pip-build-_sXoIB/pyOpenSSL/OpenSSL") = 0
lstat("/tmp/pip-build-_sXoIB/pyOpenSSL/pyOpenSSL-19.0.0.dist-info", 
{st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
lstat("/tmp/pip-build-_sXoIB/pyOpenSSL/pyOpenSSL-19.0.0.dist-info", 
{st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
openat(AT_FDCWD, "/tmp/pip-build-_sXoIB/pyOpenSSL/pyOpenSSL-19.0.0.dist-info", 
O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = 4
fstat(4, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
getdents(4, /* 7 entries */, 32768) = 216
getdents(4, /* 0 entries */, 32768) = 0
close(4)= 0
lstat("/tmp/pip-build-_sXoIB/pyOpenSSL/pyOpenSSL-19.0.0.dist-info/WHEEL", 
{st_mode=S_IFREG|0644, st_size=110, ...}) = 0
unlink("/tmp/pip-build-_sXoIB/pyOpenSSL/pyOpenSSL-19.0.0.dist-info/WHEEL") = 0
lstat("/tmp/pip-build-_sXoIB/pyOpenSSL/pyOpenSSL-19.0.0.dist-info/top_level.txt",
 {st_mode=S_IFREG|0644, st_size=8, ...}) = 0
unlink("/tmp/pip-build-_sXoIB/pyOpenSSL/pyOpenSSL-19.0.0.dist-info/top_level.txt")
 = 0
lstat("/tmp/pip-build-_sXoIB/pyOpenSSL/pyOpenSSL-19.0.0.dist-info/RECORD", 
{st_mode=S_IFREG|0644, st_size=990, ...}) = 0
unlink("/tmp/pip-build-_sXoIB/pyOpenSSL/pyOpenSSL-19.0.0.dist-info/RECORD") = 

[Bug 1817228] Re: pip install scrapy and python -m pip install scrapy cause seg fault

[Pete]

Upgraded gcc to 8 and set it to be used via sudo update-alternatives
--config gcc, still have same problem.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817228

Title:
  pip install scrapy and python -m pip install scrapy cause seg fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1817228/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1817228] Re: pip install scrapy and python -m pip install scrapy cause seg fault

[Pete]

I upgraded to Ubuntu 18.04, and now it gets to:

Successfully installed Automat-0.7.0 PyDispatcher-2.0.5 PyHamcrest-1.9.0 
Twisted-18.9.0 asn1crypto-0.24.0 attrs-18.2.0 cffi-1.12.1 constantly-15.1.0 
cryptography-2.5 cssselect-1.0.3 enum34-1.1.6 functools32-3.2.3.post2 
hyperlink-18.0.0 idna-2.8 incremental-17.5.0 ipaddress-1.0.22 lxml-4.3.1 
parsel-1.5.1 pyOpenSSL-19.0.0 pyasn1-0.4.5 pyasn1-modules-0.2.4 pycparser-2.19 
queuelib-1.5.0 scrapy-1.6.0 service-identity-18.1.0 setuptools-40.8.0 
six-1.12.0 w3lib-1.20.0 zope.interface-4.6.0
Cleaning up...
Segmentation fault (core dumped)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817228

Title:
  pip install scrapy and python -m pip install scrapy cause seg fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1817228/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1817228] [NEW] pip install scrapy and python -m pip install scrapy cause seg fault

[Pete]

Public bug reported:

Tried to install scrapy and got seg fault.  Upgraded gcc but it only
went from 7.2 to 7.3, not 8.2.  On ubuntu 17.10.  Got same error both
ways. Expected scrapy to be installed.

Last few lines on terminal were:

  Using cached 
https://files.pythonhosted.org/packages/14/2c/cd551d81dbe15200be1cf41cd03869a46fe7226e7450af7a6545bfc474c9/idna-2.8-py2.py3-none-any.whl
Collecting pycparser (from 
cffi!=1.11.3,>=1.8->cryptography->service-identity->scrapy)
Installing collected packages: queuelib, six, w3lib, cssselect, lxml, 
functools32, parsel, pyasn1, pyasn1-modules, asn1crypto, enum34, ipaddress, 
pycparser, cffi, cryptography, attrs, service-identity, setuptools, PyHamcrest, 
zope.interface, idna, hyperlink, Automat, incremental, constantly, Twisted, 
PyDispatcher, pyOpenSSL, scrapy
Segmentation fault (core dumped)

** Affects: python-pip (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: pip scrapy segmentation-fault

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817228

Title:
  pip install scrapy and python -m pip install scrapy cause seg fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1817228/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1769236] Re: CPU frequency stuck at minimum value

[Pete]

Would it be possible to include a newer version of thermald (was
probably fixed in 1.7.2 according to release notes) in Ubuntu? I have a
similar issue and it's quite annoying.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769236

Title:
  CPU frequency stuck at minimum value

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769236/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1809839] Re: Daily build 2667 broken for protocol=GP

[Pete]

Thanks

I'll join the mailing list to watch future activity..

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809839

Title:
  Daily build 2667 broken for protocol=GP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1809839/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1809839] [NEW] Daily build 2667 broken for protocol=GP

[Pete]

Public bug reported:

I'm using openconnect from the daily builds:

openconnect:
  Installed: 7.07-0~2667~ubuntu14.04.1
  Candidate: 7.07-0~2667~ubuntu14.04.1
  Version table:
 *** 7.07-0~2667~ubuntu14.04.1 0
500 http://ppa.launchpad.net/openconnect/daily/ubuntu/ trusty/main 
amd64 Packages

Version 7.07-0~2667 returns:

Failed to obtain WebVPN cookie

with the command:
openconnect --protocol=gp vpn.(myserver).com --dump-http-traffic -v

No other traffic is display.  I downloaded the source and rebuilt
version 2656 The last commit prior to 12/21 and I am running again.
Something in the 12/21 commits breaks Global Protect support.

Associated when using protocol=gp the --dump-http-traffic - didn't
add any additional information.  If I removed the --protocol=gp did see
a dump of the initial traffic to the server.

** Affects: openconnect (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/1809839

Title:
  Daily build 2667 broken for protocol=GP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1809839/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1804008] Re: Gnome Shell extensions crash [Object Meta.WindowActor (...), has been already deallocated .... from ubuntu-d...@ubuntu.com/theming.js:416]

[Pete]

Forgot to mention, you may need to use the hotkey twice to lock from
desktop.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804008

Title:
  Gnome Shell extensions crash [Object Meta.WindowActor (...), has been
  already deallocated  from ubuntu-d...@ubuntu.com/theming.js:416]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1804008/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1804008] Re: Gnome Shell extensions crash [Object Meta.WindowActor (...), has been already deallocated .... from ubuntu-d...@ubuntu.com/theming.js:416]

[Pete]

I have found a work-around to get back to desktop.

If you have locked the screen and it has hung you can lock/unlock by
using the SUPER + L hotkey (Or whatever your shortcut key is).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804008

Title:
  Gnome Shell extensions crash [Object Meta.WindowActor (...), has been
  already deallocated  from ubuntu-d...@ubuntu.com/theming.js:416]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1804008/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1807623] [NEW] Pinta doesn't allow me to select any tool other than lasso selection

[Pete]

Public bug reported:

Expected behavior: Upon clicking on a tool that tool will become selected and 
allow me to work with it.
Actual behavior: The selection jumps back to lasso and the lasso tool also is 
active and usable.

> pinta --version
1.6

> lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04

> apt-cache policy pinta
pinta:
  Installed: 1.6-2
  Candidate: 1.6-2
  Version table:
 *** 1.6-2 500
500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
500 http://archive.ubuntu.com/ubuntu bionic/universe i386 Packages
100 /var/lib/dpkg/status

** Affects: pinta (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Video demonstrating the problem"
   
https://bugs.launchpad.net/bugs/1807623/+attachment/5220744/+files/pinta-bug.mp4

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1807623

Title:
  Pinta doesn't allow me to select any tool other than lasso selection

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pinta/+bug/1807623/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1568604] Re: Mouse cursor lost when unlocking with Intel graphics

[Pete]

I am still seeing this with Mint 18.3 and 19  on at least 4 different
PCs but with nvidia graphics. Is there a fix somewhere?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568604

Title:
  Mouse cursor lost when unlocking with Intel graphics

To manage notifications about this bug go to:
https://bugs.launchpad.net/elementaryos/+bug/1568604/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1799859] Re: "pbuilder-dist create xenial" fails (Unutu 16.04) since Oct 17, 2018

[Pete]

I found a workaround for this problem.

The core issue is that BY DEFAULT cowbuilder-dist (and pbuilder-dist)
will enable multiple "pockets", including "security", "updates", and
"proposed".

It looks like the "proposed" pocket (available here:
http://archive.ubuntu.com/ubuntu/dists/xenial-proposed/main/binary-
amd64/) includes GCC version 5.4.0-6ubuntu1~16.04.11, which conflicts
with GCC version 5.3.1-14ubuntu2 (apparently required by something else
- not sure what).

When I entered my broken chroot and attempted to debug the dependency
problem, I got this:

-
root@pete-test-pc:/# apt-get install gcc-5
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 gcc-5 : Depends: cpp-5 (= 5.3.1-14ubuntu2) but 5.4.0-6ubuntu1~16.04.11 is to 
be installed
 Depends: gcc-5-base (= 5.3.1-14ubuntu2) but 5.4.0-6ubuntu1~16.04.11 is 
to be installed
 Depends: libgcc-5-dev (= 5.3.1-14ubuntu2) but 5.4.0-6ubuntu1~16.04.11 
is to be installed
E: Unable to correct problems, you have held broken packages.
-


Workaround: supply any of the flags "--release-only", "--security-only", or 
"--updates-only" to the cowbuilder-dist or pbuilder-dist commands. Using any of 
those flags will *disable* the "proposed" pocket, eg.:


cowbuilder-dist xenial create --updates-only

pbuilder-dist xenial create --updates-only

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799859

Title:
  "pbuilder-dist create xenial" fails (Unutu 16.04) since Oct 17, 2018

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1799859/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1799859] Re: "pbuilder-dist create xenial" fails (Unutu 16.04) since Oct 17, 2018

[Pete]

I've run into the same problem, although I'm using cowbuilder-dist
instead of pbuilder-dist on Ubuntu 16.04. I've attached a log.

Possibly worth noting - both 18.04 (bionic) and 14.04 (trusty) build
correctly - it's only 16.04 (xenial) that fails.

However, both "cowbuilder-dist create trusty" and "cowbuilder-dist
create bionic" also generate a similar "Distribution data outdated"
warning as the first line of output (as Alexis also mentioned).

** Attachment added: "Log of "cowbuilder-dist xenial create" on Ubuntu 16.04"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1799859/+attachment/5206128/+files/cowbuilder-dist--xenial--create.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799859

Title:
  "pbuilder-dist create xenial" fails (Unutu 16.04) since Oct 17, 2018

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1799859/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1573561] Re: /etc/default/varnish is ignored (fixed values in systemd service)

[Pete Travis]

So, as noted, I disagree with Stig's assertions.  I think it's better
for the distribution to provide the service in a way that includes
discoverable ways to adjust common commandline parameters.  Varnish
doesn't really give us a file like /etc/varnish.conf for things like
listen port parameters so the sysconfig EnvironmentFile method gives us
the next best thing.  Your approach requires a deliberate override of
the packaged service unit which could have potentially undesirable
effects in the future.  As a qualified and experienced RPM maintainer I
do not understand your aversion to using EnvironmentFile for it's
intended purpose, or your desire for a more troublesome user experience
inherent to the alternative.  We shouldn't need such dramatic and
[subjectively] non-intuitive workarounds to effect routine configuration
of your package.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573561

Title:
  /etc/default/varnish is ignored (fixed values in systemd service)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1573561/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1573561] Re: /etc/default/varnish is ignored (fixed values in systemd service)

[Pete Travis]

I disagree with this approach.  A given daemon will have command line options 
that are imperative for proper operation as a daemon, and it will have command 
line options for behavior of the service once daemonized.  If you have to 
invoke the daemon with ie `--daemonize` then it makes sense to have that 
"hardcoded" in ExecStart.  If the options affect runtime behavior but can be 
changed without breaking the way the service is instantiated, they should be 
declared in an environment file.  The cited github issue is going in the wrong 
direction, this kind of thing is what EnvironmentFile is for.  I am very 
skeptical that upstream systemd discourages the use of EnvironmentFile in this 
way...
 
Please take a look at 
https://src.fedoraproject.org/rpms/varnish/blob/master/f/varnish.service and 
https://src.fedoraproject.org/rpms/varnish/blob/master/f/varnish.params for 
some guidance on using EnvironmentFile for this use case.  I really do not like 
the idea of overriding packaged configuration files to ie change the listening 
or allocate more memory ( read: routine administration of the software ).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573561

Title:
  /etc/default/varnish is ignored (fixed values in systemd service)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1573561/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1796537] [NEW] package sgml-base 1.29 failed to install/upgrade: installed sgml-base package post-installation script subprocess returned error exit status 1

[Pete Hall]

Public bug reported:

Error message displayed after running routine upgrade process

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: sgml-base 1.29
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
AptOrdering:
 initramfs-tools:amd64: Install
 initramfs-tools-core:amd64: Install
 initramfs-tools-bin:amd64: Install
 metacity-common:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Sun Oct  7 01:13:45 2018
DuplicateSignature:
 package:sgml-base:1.29
 Processing triggers for sgml-base (1.29) ...
 cannot rename /var/lib/sgml-base/supercatalog to 
/var/lib/sgml-base/supercatalog.old: Operation not permitted at 
/usr/sbin/update-catalog line 322.
 dpkg: error processing package sgml-base (--configure):
  installed sgml-base package post-installation script subprocess returned 
error exit status 1
ErrorMessage: installed sgml-base package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2018-04-27 (163 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SourcePackage: sgml-base
Title: package sgml-base 1.29 failed to install/upgrade: installed sgml-base 
package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sgml-base (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796537

Title:
  package sgml-base 1.29 failed to install/upgrade: installed sgml-base
  package post-installation script subprocess returned error exit status
  1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sgml-base/+bug/1796537/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1791542] Re: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.0

[bata pete]

Worked for me thanx :D

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791542

Title:
  package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to
  overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also
  in package nvidia-340 340.107-0ubuntu0~gpu18.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1791542/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1726548] Re: Windows resized after resume

[Pete Vander Giessen]

I am also seeing this on a Thinkpad T480 running Bionic, with X-Windows.
The laptop has an Nvidia optimus card, for which I've setup proprietary
drivers and prime profiles using my package manager. The problem occurs
with both Intel graphics and on the Nvidia gpu.

My laptop monitor has a native resolution of 1440p, but I run it at
1080p resolution (I'm going to be very happy when and if we get 1.5x
scaling enabled for Gnome3!)

Like others in this thread, the problem occurs when I resume from
suspend. gdm3 is running at 1440p with 2x scaling. It seems like emacs,
gnome terminal, and other affected windows are picking up an appropriate
size for that as the computer resumes and unlocks ...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726548

Title:
  Windows resized after resume

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-meta/+bug/1726548/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1786202] [NEW] 18.04LTS ubuntu kernel load error rf kill switch status

[Pete]

Public bug reported:

I've just done the upgrade from 16.04LTS to 18.04LTS and the system now
hangs on boot. Booting to recovery mode shows it now hangs at the "RF
Kill Switch Status" step.

If I enter debug mode and the perform a full boot it seems to miss this
step and the boot completes

I didn't have this problem with 16.04 and my PC doesn't have wifi.

** Affects: systemd (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/1786202

Title:
  18.04LTS ubuntu kernel load error rf kill switch status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1786202/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

[Pete]

Hi,

for me it seems to work with latest bionic 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/1766969

Title:
  DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1260405] Re: Keyboard input not working in Reply To Message dialog

[Pete Ford]

I can no longer reproduce this in the version of Thunderbird I currently have 
installed: 52.8.0 (64-bit)
I think you can close it.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1260405

Title:
  Keyboard input not working in Reply To Message dialog

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1260405/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1777337] [NEW] sound says dummy output, but it doesnt appear to be detecting any hardware

[pete jack via ubuntu-bugs]

Public bug reported:

sound says dummy output, but it doesn’t appear to be detecting any
hardware

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-151-generic 3.13.0-151.201
ProcVersionSignature: Ubuntu 3.13.0-151.201-generic 3.13.11-ckt39
Uname: Linux 3.13.0-151-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity
Date: Sun Jun 17 18:00:47 2018
HibernationDevice: RESUME=UUID=5b3d6d5c-298e-41a4-a14f-98a99134bc94
InstallationDate: Installed on 2018-06-16 (0 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
IwConfig:
 eth0  no wireless extensions.
 
 lono wireless extensions.
MachineType: SAMSUNG ELECTRONICS CO., LTD. 
350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-151-generic.efi.signed 
root=UUID=8946eaec-a7d9-4d63-9527-aa6575a235c2 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-151-generic N/A
 linux-backports-modules-3.13.0-151-generic  N/A
 linux-firmware  1.127.24
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/08/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P04ABE
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: NP350V5C-A0NUK
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: BOARD REVISION 00
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP04ABE:bd11/08/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX:pvrP04ABE.007.CP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP350V5C-A0NUK:rvrBOARDREVISION00:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 
350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX
dmi.product.version: P04ABE.007.CP
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777337

Title:
  sound says dummy output, but it doesnt appear to be detecting any
  hardware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777337/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

[Pete]

Correction: I did not see the .1 in your version number.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766969

Title:
  DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

[Pete]

@Tom: Than it's not the same issue. As this is the version the bug was
reported with.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766969

Title:
  DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

[Pete]

Hi,

I'd love to help but i won't be in the affected hotel anytime soon.

So i hope some of the others could test.

Best regards, Pete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766969

Title:
  DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1727237] Re: systemd-resolved is not finding a domain

[Pete]

OK,

it's here now:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727237

Title:
  systemd-resolved is not finding a domain

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766969] Re: DNS cannot be resolved in Hotel Hotspot

[Pete]

Wireshark logs for default conf of Kubuntu and logs with workaround

** Attachment added: "wireshark logs"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+attachment/5127251/+files/dnsresolv.7z

** Tags added: dns systemd systemd-resolv

** Description changed:

  I was asked to create a new bug for this in
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it
  seems to be a different issue.
  
  I have installed the nightly image of Kubuntu Bionic from 25th of April.
  
  There systemd is in version 237-3ubuntu10.
  
+ When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg)
+ I cannot open the hotspot landing page that should give me access to the
+ WIFI. With Windows and on an Iphone it's working.
+ 
+ For the following distributions I can confirm it not working: 
+ Kubuntu 17.10
+ Kubuntu 18.04 (nightly image 25th of April 2018)
+ 
+ The logs were taken on 18.04.
+ 
  Workaround:
  sudo systemctl disable systemd-resolved.service
  sudo service systemd-resolved stop
- sudo rm /etc/resolv.conf 
- sudo nano /etc/NetworkManager/NetworkManager.conf 
-   >> add "dns=default" under [main]
+ sudo rm /etc/resolv.conf
+ sudo nano /etc/NetworkManager/NetworkManager.conf
+   >> add "dns=default" under [main]
  sudo service network-manager restart
  
+ Then I can connect to the WIFI and I see the login page in Firefox.
  
- Then I can connect to the WIFI and I see the login page in Firefox. 
- 
- To capture some data I did the following: 
-  - connect to Hotspot
-  - enter golem.de
+ To capture some data I did the following:
+  - connect to Hotspot
+  - enter golem.de
  
  Case 1: Fresh default Kubuntu install
- With a default Kubuntu install it does not work. I can connect to the WIFI 
and get IP and DNS from DHCP but I cannot resolve any hostname. When trying  to 
open the router ip directly in the browser it forwards to hotsplots.de which 
cannot be resolved. 
+ With a default Kubuntu install it does not work. I can connect to the WIFI 
and get IP and DNS from DHCP but I cannot resolve any hostname. When trying  to 
open the router ip directly in the browser it forwards to hotsplots.de which 
cannot be resolved.
  
  Case 2: With aforementioned Workaround
  I connect to the wifi, I open firefox and the login page shows up (if I 
havent been connected yet. In the capture I already was able to connect to the 
hotspot which allows immediately to connect to the webpage)

** Description changed:

  I was asked to create a new bug for this in
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it
  seems to be a different issue.
  
  I have installed the nightly image of Kubuntu Bionic from 25th of April.
  
  There systemd is in version 237-3ubuntu10.
  
  When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg)
  I cannot open the hotspot landing page that should give me access to the
  WIFI. With Windows and on an Iphone it's working.
  
- For the following distributions I can confirm it not working: 
+ For the following distributions I can confirm it not working:
  Kubuntu 17.10
  Kubuntu 18.04 (nightly image 25th of April 2018)
  
  The logs were taken on 18.04.
  
  Workaround:
  sudo systemctl disable systemd-resolved.service
  sudo service systemd-resolved stop
  sudo rm /etc/resolv.conf
  sudo nano /etc/NetworkManager/NetworkManager.conf
    >> add "dns=default" under [main]
  sudo service network-manager restart
  
  Then I can connect to the WIFI and I see the login page in Firefox.
  
  To capture some data I did the following:
   - connect to Hotspot
   - enter golem.de
  
  Case 1: Fresh default Kubuntu install
  With a default Kubuntu install it does not work. I can connect to the WIFI 
and get IP and DNS from DHCP but I cannot resolve any hostname. When trying  to 
open the router ip directly in the browser it forwards to hotsplots.de which 
cannot be resolved.
  
  Case 2: With aforementioned Workaround
  I connect to the wifi, I open firefox and the login page shows up (if I 
havent been connected yet. In the capture I already was able to connect to the 
hotspot which allows immediately to connect to the webpage)
+ 
+ PS: I'll be in this hotel till Friday 27th if more information are
+ required.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766969

Title:
  DNS cannot be resolved in Hotel Hotspot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766969] [NEW] DNS cannot be resolved in Hotel Hotspot

[Pete]

Public bug reported:

I was asked to create a new bug for this in
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it
seems to be a different issue.

I have installed the nightly image of Kubuntu Bionic from 25th of April.

There systemd is in version 237-3ubuntu10.

When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg)
I cannot open the hotspot landing page that should give me access to the
WIFI. With Windows and on an Iphone it's working.

For the following distributions I can confirm it not working:
Kubuntu 17.10
Kubuntu 18.04 (nightly image 25th of April 2018)

The logs were taken on 18.04.

Workaround:
sudo systemctl disable systemd-resolved.service
sudo service systemd-resolved stop
sudo rm /etc/resolv.conf
sudo nano /etc/NetworkManager/NetworkManager.conf
  >> add "dns=default" under [main]
sudo service network-manager restart

Then I can connect to the WIFI and I see the login page in Firefox.

To capture some data I did the following:
 - connect to Hotspot
 - enter golem.de

Case 1: Fresh default Kubuntu install
With a default Kubuntu install it does not work. I can connect to the WIFI and 
get IP and DNS from DHCP but I cannot resolve any hostname. When trying  to 
open the router ip directly in the browser it forwards to hotsplots.de which 
cannot be resolved.

Case 2: With aforementioned Workaround
I connect to the wifi, I open firefox and the login page shows up (if I havent 
been connected yet. In the capture I already was able to connect to the hotspot 
which allows immediately to connect to the webpage)

PS: I'll be in this hotel till Friday 27th if more information are
required.

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: dns systemd systemd-resolv

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766969

Title:
  DNS cannot be resolved in Hotel Hotspot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1727237] Re: systemd-resolved is not finding a domain

[Pete]

I freshly installed the latest Kubuntu Bionic nightly image from today
night. That should be rather close to tomorrow's release.

There systemd 237-3ubuntu10 is installed. However, it still does not
work. I can not resolve dns out of the box in my Hotel wifi (Quality
Hotel Augsburg, Germany).

The support of the hotspot provider forwarded me to this bug and assumed
it to be solved in 18.04.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727237

Title:
  systemd-resolved is not finding a domain

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1762140] [NEW] [Mate]upgrade error attempt 2

[bata pete]

Public bug reported:

I've disabled all non-Canonical ppa's did a apt dist-upgrade and then
ran sudo do-release-upgrade -d and still it still fails

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.24
ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
Uname: Linux 4.4.0-119-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: MATE
Date: Sun Apr  8 10:16:00 2018
InstallationDate: Installed on 2016-07-19 (627 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to xenial on 2018-04-08 (0 days ago)

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug dist-upgrade xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762140

Title:
  [Mate]upgrade error attempt 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1762140/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1761952] [NEW] [Mate]upgrade error

[bata pete]

Public bug reported:

Shouldn't there be a way to see what is wrong other than giving a user a
"there is an error because there was an error" type feedback?

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.24
ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
Uname: Linux 4.4.0-119-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: MATE
Date: Sat Apr  7 10:27:02 2018
InstallationDate: Installed on 2016-07-19 (626 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to xenial on 2018-04-07 (0 days ago)

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug dist-upgrade xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761952

Title:
  [Mate]upgrade error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1761952/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 608162] Re: GNOME Keyring Daemon stops panel's shutdown

[Pete]

Problem occurs 100% of the time on two Mint Cinnamon 64 bit machines
after the latest round of updates when shutting down or restarting from
whisker menu. 'shutdown (-r) now' works without an error.

The most commonly reported 'fix' for this problem is purging old
kernels. I just reinstalled 18.3 Cinnamon 64 from scratch on one and
then installed all the updates. There were only 2 kernels. I removed
4.10 4.13.0-36 is the only one installed.  It did not fix the problem. I
did not have the problem before the last round of updates.


Also on another computer with 18.2 which has not been turned on for a while I 
never had the problem until I just installed updates. It is using 4.10.0-33 
kernel.  4.8.0.53, 4.10.0-33, and 4.13.0-36 are installed.

I had no problem with on two 18.3 XFCE 64 bit machines. One I last
used/updated Sunday 3/4 or another I just updated (including latest
kernel) as of 3/8/18 0245Z.

All computers are set for autologin. I tried turning autologin off on
one Cinnamon but that had no effect.

It appears there is something in the recent updates for Cinnamon that is
causing this problem.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/608162

Title:
  GNOME Keyring Daemon stops panel's shutdown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/608162/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1377653] Re: HDMI sound output not detected / NVIDIA optimus laptop

[Pete]

I can confirm that #19 works, as well. Also applied the suggestions in #24.
Ubuntu 17.10 on a Lenovo Ideapad Y910-17ISK with a GTX 1070.
I don't notice any flicker or any problem. The audio device has just appeared, 
and everything works fine now :-) 
Thanks a lot!!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1377653

Title:
  HDMI sound output not detected / NVIDIA optimus laptop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1377653/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1727237] Re: systemd-resolved is not finding a domain

[Pete]

I too am still encountering this issue.

Since I can't resolve the webpage to the captive portal I have to
manually enter its IP 1.1.1.1

Then accept the agreement. However afterwards DNS still fails to resolve
web-pages.

Today I edited /etc/resolv.conf as before, adding Google DNS to show
this.

nameserver 127.0.0.53
nameserver 8.8.8.8

But I noticed resolving DNS was slow, because 127.0.0.53 was failing.
And after timing out it goes to the Google DNS 8.8.8.8.

After removing 127.0.0.53 in the file and only using "nameserver
8.8.8.8" everything works fine and quickly.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727237

Title:
  systemd-resolved is not finding a domain

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1727237] Re: systemd-resolved is not finding a domain

[Pete]

I also have been experiencing this. Connecting to WiFi network that uses
any captive portal fails.

I dual boot with Windows, and everything is fine in Windows.

System: 
Ubuntu 17.10 (Clean install)

Behavior:
After authenticating with the portal and connecting I cannot resolve DNS.

My work around (after a lot of digging) was to edit "/etc/resolv.conf"

And add "nameserver 8.8.8.8" (Google Public DNS)

So my nameserver looked liked:

nameserver 127.0.0.53
nameserver 8.8.8.8

I had to do this after every reboot obviously.

Also very peculiar:
I have been using this work-around every day since installing 17.10 one week 
ago. However, I connected to a regular home WiFi network (non-captive portal) 
fine last night. Then after returning to my work captive-portal WiFi network 
its now connecting and resolving DNS successfully. Without having to update my 
/etc/resolv.cong. I don't understand why...

Wanted to mention while searching forums and bug reports I came across
many reported bugs that are likely duplicates of this issue. Where users
are reporting spotty or intermittent WiFi issues etc. Many think its
kernel and driver issues, while this isn't the case.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727237

Title:
  systemd-resolved is not finding a domain

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1710382] Re: Wireless network frequently drops in 17.10

[Pete]

I am also having the same problem w/ 17.10.

Maybe be a duplicate of bug 1726187 and 1736690.

I am also having issues with my WiFi connection dropping out, freezing,
etc.

I see other bugs reported as well for 17.10 / 18.04 Ubunutu.

I am using latest 17.10 build, clean install.
Laptop: Yoga 11e
Kernel: 4.13.0-21-generic
WiFi: Network controller: Intel Corporation Wireless 7265 (rev 61)

Occasionally it works when connecting, then stops.

What I find most peculiar is that I discovered the DNS appears to
intermittently stop 'while' I am using the computer online.

If I manually edit "/etc/resolv.conf" (which you shouldn't have to do),
and change "nameserver 127.0.0.53" to "nameserver 8.8.8.8".

Then save, everything works fine and is stable until the next reboot!

I don't think this is a driver/kernel issue, its almost like resolv.conf
is broken.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710382

Title:
  Wireless network frequently drops in 17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1710382/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1726187] Re: After 17.04 -> 17.10 upgrade, wifi often freezes

[Pete]

I am also having issues with my WiFi connection dropping out, freezing,
etc.

I see other bugs reported as well for 17.10 / 18.04 Ubunutu.

I am using latest 17.10 build, clean install.
Laptop: Yoga 11e
Kernel: 4.13.0-21-generic
WiFi:  Network controller: Intel Corporation Wireless 7265 (rev 61)

Occasionally it works when connecting, then stops.

What I find most peculiar is that I discovered the DNS appears to
intermittently stop while I am using the computer.

If I manually edit "/etc/resolv.conf" (which you shouldn't have to do),
and change "nameserver 127.0.0.53" to "nameserver 8.8.8.8".

Once saved everything works fine and is stable until the next reboot.

I don't think this is a driver/kernel issue, its almost like resolv.conf
is broken.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726187

Title:
  After 17.04 -> 17.10 upgrade, wifi often freezes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1726187/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1704765] Re: can't drag file from desktop to folder window on Artful

[Pete]

I confirm this issue as well. Using latest build of 17.10 and updated.
It requires me to log off/on to get things working again.

I found multiple duplicate bugs on this issue, and yes...wonder why its
not fixed?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1704765

Title:
  can't drag file from desktop to folder window on Artful

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1704765/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1741777] Re: drag and drop between desktop and nautilus doesn't work

[Pete]

I confirm I have this exact problem. Using latest build of Ubuntu 17.10
(Wayland)from Jan 2018.

Note: This bug also seems very similar to this one.

https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1729887

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741777

Title:
  drag and drop between desktop and nautilus doesn't work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1741777/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1741777] Re: drag and drop between desktop and nautilus doesn't work

[Pete]

Looks like this may be the same issue as this bug still not resolved.

https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1704765

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741777

Title:
  drag and drop between desktop and nautilus doesn't work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1741777/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1682744] Re: Connecting to wifi 5GHz network causes iwlwifi firmware/driver error. Intel Wireless 7260

[Pete]

I believe I am having the same issue on Ubuntu 17.10. Using Lenovo Yoga
11e, w/ Intel 7265 wireless.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682744

Title:
  Connecting to wifi 5GHz network causes iwlwifi firmware/driver error.
  Intel Wireless 7260

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1682744/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

[Pete Hildebrandt]

Ubuntu: 17.10
Mainline Kernel: 4.14.7

Still not working :(

anti-egos fix didn't help.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589008

Title:
  Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589008/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1723202] Re: Ubuntu AppIndicators extension doesn't work after suspend/resume cycle

[Pete Vander Giessen]

This seems to be fixed in the latest update!

** Changed in: gnome-shell-extensions (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723202

Title:
  Ubuntu AppIndicators extension doesn't work after suspend/resume cycle

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extensions/+bug/1723202/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1584457] Re: gsd-backlight-helper spamming the logs since upate to 16.04

[Pete Vander Giessen]

@zmoazeni: Stopping the service does indeed stop the log spam on my
machine. Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1584457

Title:
  gsd-backlight-helper spamming the logs since upate to 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1584457/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1280372] Re: Unknown Qt application causes HUD / libdbusmenu-qt to use 100% CPU

[Pete Woods]

** No longer affects: hud

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1280372

Title:
  Unknown Qt application causes HUD / libdbusmenu-qt to use 100% CPU

To manage notifications about this bug go to:
https://bugs.launchpad.net/libdbusmenu-qt/+bug/1280372/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1263926] Re: libqtdbustest and libqtdbusmock fail to build on i386

[Pete Woods]

** Changed in: libqtdbusmock
   Status: Fix Committed => Fix Released

** Changed in: libqtdbustest
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1263926

Title:
  libqtdbustest and libqtdbusmock fail to build on i386

To manage notifications about this bug go to:
https://bugs.launchpad.net/libqtdbusmock/+bug/1263926/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1364842] Re: Unable to install in an armhf chroot

[Pete Woods]

** Changed in: libqtdbusmock (Ubuntu)
 Assignee: Pete Woods (pete-woods) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1364842

Title:
  Unable to install in an armhf chroot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libqtdbusmock/+bug/1364842/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1161932] Re: Voice tests don't work on Jenkins

[Pete Woods]

** Changed in: hud
 Assignee: Pete Woods (pete-woods) => (unassigned)

** Changed in: hud (Ubuntu)
 Assignee: Pete Woods (pete-woods) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161932

Title:
  Voice tests don't work on Jenkins

To manage notifications about this bug go to:
https://bugs.launchpad.net/hud/+bug/1161932/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs