For info, when I run "sudo apt --fix-broken install" it sometimes fails
with a segmentation fault. Also, it seems to report "Operation not
permitted" errors on a different drivers each time I run it. It's not
repeatable.
Is there a way that I can uninstall the 5.3.0-24 kernel (apt purge
doesn't wo
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflo
Just to get confirmation, this bug was only introduced as of Stein,
right? It's not present in Rocky or earlier?
Gage, assuming the above is true, and if nobody has any other concerns
about your proposed impact description in comment #17, you can probably
go ahead and request a CVE assignment for
Public bug reported:
When I run tests via Selenium error modal is shown on Chrome run.
In Russian:
Ошибка при загрузке разширения
Не удалось загрузить расширение из: . Файл манифеста отсутствует или недоступен
для чтения
Translation:
Error while loading extension
Couldn't load extension from: .
[VERIFICATION DISCO]
I have installed Disco, layout /usr on it's on LV, and at reboot same
problem as describe in the impact section. Server stuck in trying to
mount /usr due to lack of LVM activation.
At the initramfs prompt, I ran 'lvm vgchange -ay' to boot properly. I
installed the disco-propo
I am not sure if there are two different problems:
- the lagginess (repeated freezing for let's say some 100ms) when increasing
cache/buf makes the kernel swap too much (which is clearly different from a
system that suffers from heavy swapping, far worse)
- the complete and final freeze of the G
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
The solution to my problem was given to me in #ubuntu on Freenode.
Kernel parameter radeon.dpm=0. That's dynamic power management. I think
the clue was that everything works fine when the laptop is not plugged
in, so the fine young man probably thought there was a bug in dynamic
power management. D
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-bionic
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
F
Which gui? well: KDE, Xorg, Intel driver, sddm. What exactly are you
asking for?
I had a freeze again and had the syslog running in a toplevel window with
GRUB_CMDLINE_LINUX="drm.debug=0x1e log_buf_len=1M
Did not get any message that would explain the freeze. And did not ever get a
GPU HANG agai
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-xenial
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
F
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-sta
There are two release branches: 1 and 2. 1 is production-quality, well
tested by many users. 2 is still in alpha stage, with beta planned for
end of December, release for March. It includes support for not yet
shipping hardware.
Both are available for review: branch 1 is in Debian unstable and
** Changed in: rhythmbox
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/947038
Title:
Rhythmbox: Add to Playlist option creates a playlist with an empty
name
To manag
** Changed in: rhythmbox
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/500773
Title:
Not all audio CD's contains "songs", use "track" instead
To manage notifications a
Public bug reported:
When running the official Ubuntu 18.04 cloud image in VIO (VMware
Integrated OpenStack, see [1]), data source `Ec2` is not detected as
working so `cloud-init` does not run.
As a result, it is impossible to log in or connect to the running image
via SSH. In other words, VMs s
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-xenial
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
F
>From the `ds-identify.log` file in the uploaded archive, one can see
that `ds-identify` rejects the `Ec2` metadata source and disables
`cloud-init`:
Running on vmware but rpctool query returned 1: No value found
is_ds_enabled(IBMCloud) = true.
ec2 platform is 'Unknown'.
No ds foun
I am providing here the additional information that were requested in
https://bugs.launchpad.net/ubuntu/+source/open-vm-
tools/+bug/1760776/comments/17
I'm attaching the collected cloud-init logs; here is the output of
commands.
The Linux kernel correctly determines the hypervisor is VMware (exce
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux-gcp - 5.3.0-1009.10
---
linux-gcp (5.3.0-1009.10) eoan; urgency=medium
* eoan/linux-gcp: 5.3.0-1009.10 -proposed tracker (LP: #1852227)
* autofs module missing from linux-modules in 5+ kernels (LP: #1849848)
- [Config] Update autofs4 pa
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux-gcp - 5.3.0-1009.10
---
linux-gcp (5.3.0-1009.10) eoan; urgency=medium
* eoan/linux-gcp: 5.3.0-1009.10 -proposed tracker (LP: #1852227)
* autofs module missing from linux-modules in 5+ kernels (LP: #1849848)
- [Config] Update autofs4 pa
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux-gcp - 5.3.0-1009.10
---
linux-gcp (5.3.0-1009.10) eoan; urgency=medium
* eoan/linux-gcp: 5.3.0-1009.10 -proposed tracker (LP: #1852227)
* autofs module missing from linux-modules in 5+ kernels (LP: #1849848)
- [Config] Update autofs4 pa
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
*** This bug is a duplicate of bug 1850486 ***
https://bugs.launchpad.net/bugs/1850486
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
*** This bug is a duplicate of bug 1850481 ***
https://bugs.launchpad.net/bugs/1850481
This bug was fixed in the package linux-gcp - 5.3.0-1009.10
---
linux-gcp (5.3.0-1009.10) eoan; urgency=medium
* eoan/linux-gcp: 5.3.0-1009.10 -proposed tracker (LP: #1852227)
* autofs mod
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux-gcp - 5.3.0-1009.10
---
linux-gcp (5.3.0-1009.10) eoan; urgency=medium
* eoan/linux-gcp: 5.3.0-1009.10 -proposed tracker (LP: #1852227)
* autofs module missing from linux-modules in 5+ kernels (LP: #1849848)
- [Config] Update autofs4 pa
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
This bug was fixed in the package linux - 5.3.0-24.26
---
linux (5.3.0-24.26) eoan; urgency=medium
* eoan/linux: 5.3.0-24.26 -proposed tracker (LP: #1852232)
* Eoan update: 5.3.9 upstream stable release (LP: #1851550)
- io_uring: fix up O_NONBLOCK handling for sockets
- d
Public bug reported:
The grub-efi-amd64-signed package failed to install into / target/.
without the GRUB boot loader,the installed system will not boot.
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
Unam
Public bug reported:
I recently did the automated software update on my computer. It required
that I restart my computer. Upon restarting, the touchpad was no longer
responsive. Left and Right clicking doesn't work either. This is a Dell
laptop.
This information is from the sticker on the bottom
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-sta
I rebooted (so no apps are running really), locked computer, and
unplugged all USB devices.
The screen eventually goes dark, but the monitors never get told to be
"off"/standby (lights stay green on them), and I see the mouse pointer.
I can also see the back panel lighting through the screen (as
/etc/hosts:
127.0.0.1 localhost
127.0.1.1 kato i7
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
$ systemd-resolve --status
Global
DNS Serv
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner.
This release of Ubuntu is no longer receiving maintenance updates. If
this is still an issue using a maintained version of Ubuntu please let
us know otherwise this report can be left to expire in a
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner.
This release of Ubuntu is no longer receiving maintenance updates. If
this is still an issue using a maintained version of Ubuntu please let
us know otherwise this report can be left to expire in a
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner.
This release of Ubuntu is no longer receiving maintenance updates. If
this is still an issue using a maintained version of Ubuntu please let
us know otherwise this report can be left to expire in a
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855460
Title:
Touchpad Not Working After Update
To manag
Fyi on stable point releases: https://review.opendev.org/#/c/697688/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852599
Title:
Cannot delete TLS Terminated listener if container has been deleted
Same issue on my laptop:
[8.498382] [ cut here ]
[8.498387] Could not determine valid watermarks for inherited state
[8.498448] WARNING: CPU: 2 PID: 185 at
/build/linux-dWhjJj/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537
intel_modeset_init+0xfcf/0x10
*** Bug 1597218 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697122
Title:
Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel
s
** Changed in: ubuntu-z-systems
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/1847590
Title:
Check for CPU Measurement sampling
To manage notifications
** Changed in: ubuntu-z-systems
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/1848492
Title:
Change Config Option CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE fo
You missed contents of /etc/resolv.conf
Also paste contents of /etc/systemd/resolved.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853669
Title:
systemd resolves own hostname to link local ip
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
** Also affects: pcre2 (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946221
Importance: Unknown
Status: Unknown
** No longer affects: rspamd (Debian)
** Changed in: pcre2 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you ar
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy
Whitcroft (apw)
--
You received this bug notification because you are a me
Verified the fix works on eoan with my 9360 running kernel 5.3.0-25
proposed. Updated the tag. Hope I did this right :S
** 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 subscrib
I will send a patch making vfio-pci built-in.
** Also affects: linux (Ubuntu Focal)
Importance: Medium
Status: Opinion
** Changed in: linux (Ubuntu Focal)
Status: Opinion => In Progress
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Thadeu Lima de Souza Casca
201 - 300 of 583 matches
Mail list logo