This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1860306
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** 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: ubuntu-z-systems
Status: Incomplete => In Progress
** Changed in: qemu (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
The mentioned commit 6ab79a20af3a7b3bf610ba9aebb446a9f0b05930 is in qemu 4.1
and later.
Since we will have qemu 4.2 in 20.04 please retry with that once available.
I'll set a bug tak reference in the changelog of the update.
** Tags removed: qemu-19.10
** Tags added: qemu-20.04
--
You received
https://sportinfo.com.ng/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/988799
Title:
Precise freezes under heavy i/o
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
[366338.166585] input: UVC Camera (eb1a:299f) as
/devices/pci:00/:00:08.1/:0d:00.3/usb5/5-4/5-4:1.0/input/input41
[366338.166652] usbcore: registered new interface driver uvcvideo
[366338.166652] USB Video Class driver (1.1.1)
[366357.978516] usbcore: deregistering interface driver uvc
Public bug reported:
Upon installation of kernel update 5.3.0.26.95, after a reboot,
Second screen would not come on and nvidia control panel was missing majority
of options
Graphics driver settings could not be changed and upon reinstallation attempt
of nvidia driver 390, installation failed an
** 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
https://sportinfo.com.ng/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/620074
Title:
Thrashing turns system unusable
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
** 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
Image is not ready.
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-snapdragon in Ubuntu.
https://bugs.launchpad.net/bugs/1858544
Title:
No official image for this kernel.
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/185852
Hardware Certification have begun testing this -proposed kernel.
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-snapdragon in Ubuntu.
Hardware Certification have begun testing this -proposed kernel.
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-snapdragon in Ubuntu.
** 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
Hardware Certification have begun testing this -proposed kernel.
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
http
Hardware Certification have begun testing this -proposed kernel.
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
http
Hardware Certification have begun testing this -proposed kernel.
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
http
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860303
Title:
Backlight brightness cannot be
Public bug reported:
I cannot adjust the screen brightness using the keyboard keys or
changing /sys/call/backlight/intel_backlight/brightness values. I've
only been able to adjust the backlight using xrandr.
Followed bug report on
https://wiki.ubuntu.com/Kernel/Debugging/Backlight#Diagnostic_Tec
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-390 (Ubuntu Eoan)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in
*** This bug is a duplicate of bug 1830961 ***
https://bugs.launchpad.net/bugs/1830961
** Summary changed:
- package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed
nvidia-dkms-390 package post-installation script subprocess returned error exit
status 10
+ package nvid
** Also affects: nvidia-graphics-drivers-390 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1830961
Title:
Kern
*** This bug is a duplicate of bug 1851162 ***
https://bugs.launchpad.net/bugs/1851162
It appears the Nvidia-390 kernel driver doesn't support kernel 5.3 and
is not loading anymore.
** Summary changed:
- Resolution incorrect after updating kernel to 5.3
+ Nvidia-390 resolution incorrect afte
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubunt
** Summary changed:
- nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19
+ nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19 [error:
redefinition of ‘list_is_first’]
** Tags added: eoan
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Importance: Und
*** This bug is a duplicate of bug 1851162 ***
https://bugs.launchpad.net/bugs/1851162
** Summary changed:
- dpkg-reconfigure nvidia-dkms-390 fails for kernel 5.3.0.-26
+ dpkg-reconfigure nvidia-dkms-390 fails for kernel 5.3.0.-26 [error:
redefinition of ‘list_is_first’]
** This bug has
*** This bug is a duplicate of bug 1851162 ***
https://bugs.launchpad.net/bugs/1851162
It looks like this will be bug 1851162, or bug 1830961
** This bug has been marked a duplicate of bug 1851162
nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19 [error:
redefinition of
You have been subscribed to a public bug:
Updated kernel from 5.0 to 5.3. After reboot, resolution appears to be
something like 640 x 480. Accessed (with difficulty) display settings.
Monitor is shown as unknown device. Tried reinstalling kernel, problem
remains. Can still boot successfully into p
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1859071
Title:
Native mode 2560x1080 is rando
Thanks but that crash report is not relevant here.
Please follow the instructions in comment #8.
Please also update your system by running:
sudo apt update
sudo apt full-upgrade
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Great, thanks. Indeed the native mode of the monitor is missing from
that list so this is a kernel or hardware problem.
I assume the same command /usually/ shows more modes..?
** No longer affects: xorg-server (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Summary ch
There is no "fix" for this bug. You need to ignore the previous
messages.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1836858
Title:
i915: Display flickers (monitor loses signal brief
*** This bug is a duplicate of bug 1745345 ***
https://bugs.launchpad.net/bugs/1745345
** Tags added: nouveau
** Summary changed:
- X11 crashed when attempting to open GtkWebKit- and gstreamer-based
applications (as Yelp, Cheese, Budgie and MATE Welcome)
+ [nouveau] X11 crashed when attempt
Public bug reported:
After the update from 5.0 to 5.3 the dkms reconfigure of the nvidia-390 kernel
module fails.
The problem seems to be in a conflict between the "list_is_first" routine in
the module and the new kernel, which causes a compile error. I will upload
/var/lib/dkms/nvidia/390.116/
On 2020-01-19 16:15:58, aaronleung wrote:
> My OS have this bug, i try to install kernel 5.4 in my linuxmint19.3,
> bug, instailing not found samething with from /lib/firmware/i915/ ,again.
> i try to download from
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/
zfs-linux (0.6.5.6-2) unstable; urgency=medium
...
* Scrub all healthy pools monthly from Richard Laager
So Debian stretch, but not Ubuntu 16.04.
Deleting the file should be safe, as dpkg should retain that. It sounds
like you never deleted it, as you didn’t have it before this upgrade. So
it w
Thank you advice.
but I do not use nomodeset option.
I use ipv6.disable=1 option.
please show attachment file(grub).
** Attachment added: "my boot option /etc/default/grub"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860196/+attachment/5321568/+files/grub
--
You received this bug
@rlaager ref for "long time ago"? (Looking for release notes and
specific version)
I've been reasonably diligent in monitoring my pool scrub activity, I
would "guess" that maybe in the last 2-3 months I may have lost track.
But also I only upgraded from Ubuntu 16.04 LTS sometime late-2019 Fall
(ii
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860284
Title:
thinkpad thunderbolt 3 dock ge
** Attachment added:
"ubuntu_5.3.0-26_working_dmesg_dock_plugged_before_boot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860284/+attachment/5321565/+files/ubuntu_5.3.0-26_working_dmesg_dock_plugged_before_boot.txt
--
You received this bug notification because you are a member
** Attachment added:
"ubuntu_5.3.0-26_notworking_lspci_dock_plugged_after_boot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860284/+attachment/5321563/+files/ubuntu_5.3.0-26_notworking_lspci_dock_plugged_after_boot.txt
--
You received this bug notification because you are a mem
Public bug reported:
I have thinkpad thunderbolt 3 dock gen2 dock I am trying to use with a
New Lenovo Yoga C940 laptop.
- The dock works fine when plugged-in before boot.
- The dock does NOT work when plugged after the system booted.
- The dock does NOT work when plugged-in at boot, subsequently
** Attachment added:
"ubuntu_5.3.0-26_working_lsusb_dock_plugged_before_boot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860284/+attachment/5321567/+files/ubuntu_5.3.0-26_working_lsusb_dock_plugged_before_boot.txt
--
You received this bug notification because you are a member
** Attachment added:
"ubuntu_5.3.0-26_working_lspci_dock_plugged_before_boot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860284/+attachment/5321566/+files/ubuntu_5.3.0-26_working_lspci_dock_plugged_before_boot.txt
--
You received this bug notification because you are a member
** Attachment added:
"ubuntu_5.3.0-26_notworking_dmesg_dock_plugged_after_boot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860284/+attachment/5321562/+files/ubuntu_5.3.0-26_notworking_dmesg_dock_plugged_after_boot.txt
--
You received this bug notification because you are a mem
** Attachment added:
"ubuntu_5.3.0-26_notworking_lsusb_dock_plugged_after_boot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860284/+attachment/5321564/+files/ubuntu_5.3.0-26_notworking_lsusb_dock_plugged_after_boot.txt
--
You received this bug notification because you are a mem
My OS have this bug, i try to install kernel 5.4 in my linuxmint19.3,
bug, instailing not found samething with from /lib/firmware/i915/ ,again.
i try to download from
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/.
I download 5 .bin file and move to /lib/firmware
I got the same situation and output.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1824886
Title:
Battery level stu
The issue is more generic - Yelp and Cheese crash in the VirtualBox on
MATE, Xfce, Budgie and GNOME FlashBack (metacity) sessions.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1796437
Ti
** Description changed:
-
+ Legacy BSD PTYs have been replaced by UNIX 98 PTYs a long time ago.
+ Disable legacy BSD PTY support as it is no longer needed.
+
+ This config option is recommended by the Kernel Self Protection
+ Project[1] and a 2019 study performed by Capsule 8 shows that it is
+
** Description changed:
-
+ We should disable CONFIG_USELIB to make the uselib(2) system call
+ unreachable in an effort to reduce the kernel attack surface.
+
+ The system call is only used by very old libc implementations and is
+ unlikely to be used today.
+
+ This config option is recommend
** Description changed:
-
+ We should enable CONFIG_IO_STRICT_DEVMEM to restrict userspace access of
+ active io-memory ranges.
+
+ This could impact kernel debugability. In that case, you may reboot with
+ iomem=relaxed on the kernel commandline to override this setting.
+
+
+ This config opt
** Summary changed:
- X11 crashed when attempting to open Budgie and MATE Welcome
+ X11 crashed when attempting to open GtkWebKit- and gstreamer-based
applications (as Yelp, Cheese, Budgie and MATE Welcome)
--
You received this bug notification because you are a member of Kernel
Packages, which
** Description changed:
-
+ We should enable CONFIG_DEBUG_NOTIFIERS to ensure that notifier functions are
present in the core kernel text or module text sections before calling
+ those functions.
+
+ If an invalid function pointer is detected, a warning is issued and the
+ function is not calle
** Description changed:
-
+ Enable CONFIG_DEBUG_SG to perform sanity checks when performing
+ operations on scatterlists. If a sanity check fails a loud warning is
+ printed to the logs.
+
+ This change may help in detection of an attack that relies on
+ scatterlist manipulation.
** Description
** 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
@john This problem was meanwhile worked around by setting
radeon.agp.mode=-1 as default in recent kernels (=> 5.0 ?). So you don't
need to fiddle around with your settings here. Unfortunately Ubuntu ppc
support is dead, only ppc64le option is maintained.
But there are other distros (Void, Adelie).
[366338.166585] input: UVC Camera (eb1a:299f) as
/devices/pci:00/:00:08.1/:0d:00.3/usb5/5-4/5-4:1.0/input/input41
[366338.166652] usbcore: registered new interface driver uvcvideo
[366338.166652] USB Video Class driver (1.1.1)
[366357.978516] usbcore: deregistering interface driver uvc
** Description changed:
-
+ We should enable CONFIG_DEBUG_CREDENTIALS to perform sanity checks, such as
verifying usage counts and proper magic values, when handling cred
+ structs. If a cred sanity check fails a loud warning is printed to the
+ logs.
+
+ The config option raises the bar on the
** Description changed:
-
+ We should turn on CONFIG_DEBUG_LIST which does some sanity checking on the
+ surrounding linked list elements when adding or removing an element. If the
sanity check fails, the list manipulation operation is not and a loud warning
is printed to the logs in the form o
** 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
You use nouveau, but have set the boot option nomodeset. So it is your
fault.
Bionic with kernel 5.3.0-26 and nouveau work fine.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860196
Tit
With the new kernel update this issue happens to me. No connection to
wifi. Not possible. I am using a Clevo notebook, which was rebranded by
Tuxedo.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
65 matches
Mail list logo
