I tried both 5.2.11 and 5.3-rc6. Same result with both.
--
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/1839856
Title:
Screen resolution on external monitor won't go above 2560 x 1080
St
Public bug reported:
Ubuntu 18.04 w/ kernel 4.18.0-15 or 4.19.28 w/ nouveau driver on top of
Xen 4.11.1 regularly deadlocks system. It's reachable via network for a
bit, then becomes completely unresponsive.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: kerneloops 0.12+git20140509-6ubuntu
I reported this incorrectly, since the actual traces aren't included.
Here's the kernel log.
** Attachment added: "kern.log-20190313"
https://bugs.launchpad.net/ubuntu/+source/kerneloops/+bug/1819918/+attachment/5245858/+files/kern.log-20190313
--
You received this bug notification because y
** Attachment added: "Here's the 4.18.0-15 kernel log, showing a stuck thread"
https://bugs.launchpad.net/ubuntu/+source/kerneloops/+bug/1819918/+attachment/5246718/+files/kern.log-20190308
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
This broke my ability to build the Xenial HWE kernel offline using the
default kernel configuration (trying to build binary-lowlatency
specifically). Building a package shouldn't require me to have an
internet connection.
I am also concerned about complying with the CDDL license since the ZFS
sour
Public bug reported:
The target subsystem (LIO) can hang if multiple threads try to destroy
iSCSI sessions simultaneously. This is reproducible on systems that have
multiple targets with initiators regularly connecting/disconnecting.
This may happen when a "targetcli iscsi/iqn.../tpg1 disable" co
** Attachment added: "dmesg output shortly after booting"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871688/+attachment/5349845/+files/dmesg.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
** Attachment added: "output of `lspci -vvnn`"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871688/+attachment/5349846/+files/lspci-vvnn.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
** Attachment added: "contents of /proc/version_signature"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871688/+attachment/5349844/+files/version.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
** Tags added: bionic focal
** Description changed:
The target subsystem (LIO) can hang if multiple threads try to destroy
iSCSI sessions simultaneously. This is reproducible on systems that have
multiple targets with initiators regularly connecting/disconnecting.
This may happen when
The only machines I've reproduced this bug on are running Xenial. For
the past few months, I've been applying these patches to the Xenial HWE
kernels and building packages for my dev/test systems.
These systems frequently add and remove targets (around 125 per hour)
with separate initiators connec
I built and installed the package on one of my Xenial systems from the
source available here:
https://launchpad.net/ubuntu/+source/linux/4.15.0-100.101
If the system is still stable a day from now, is it okay for me to set
the 'verification-done-bionic' tag, even though I'm testing on Xenial?
--
My Xenial system is still stable after almost two days with the kernel
package I built from the proposed Bionic kernel's source.
--
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/1871688
Titl
I installed the proposed Bionic packages on my Xenial system and have
confirmed that basic functionality is working properly. If the system
remains stable for >24h, I will consider the issue to be fixed in this
kernel.
--
You received this bug notification because you are a member of Kernel
Packa
The Xenial system that I installed the binary packages from the proposed
Bionic repository on has been running properly and stable since the 7th.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
.3.7
Uname: Linux 5.3.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: matt 2211 F.... pulseaudio
/dev/snd/controlC1: matt 2211 F.... pulseaudi
a
ApportVersion: 2.20.11-0ubuntu8.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: gdm7450 F pulseaudio
matt 8011 F pulseaudio
/dev/snd/controlC0: gdm7450 F pulseaudio
ma
I believe this bug affected my Dell XPS 13" 7390 (2-in-1). I also
verified this by updating to use the bionic-proposed linux-firmware
package and bluetooth now works! thank you all so much!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
After some more research I found out that this is actually due to an
unimpelmented feature in Nvidia's drivers.
On this model of laptop, the video output ports all connect directly to
the discrete Nvidia GPU, and Nvidia's drivers do not yet support the GPU
being used as a sink from the integrated
nature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: matt 2211 F pulseaudio
/dev/snd/controlC1
8.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: matt 2211 F pulseaudio
/dev/snd/controlC1: matt 2211 F pulseaudio
/dev/snd/controlC0: matt 2211 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 18 13:44:3
ules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: matt 2211 F pulseaudio
/dev/snd/controlC1: matt 2211 F pulseaudio
/dev/snd/controlC0: matt 2
I had this problem occur recently and was able to work with one of my
System Administrators to narrow it down. I saw the floppy text in the
output so I asked my Sys Admin to connect the Floppy Drive in VCenter to
the VMs that were having this issue (3 new 18.04 installs) and the issue
is now resol
Public bug reported:
In a recent driver, Nvidia finally added Linux support for render
offload, where most graphics are rendered on the CPU-onboard GPU and
only certain applications are rendered on the discrete Nvidia GPU. I
know that Ubuntu 19.10 started shipping some updated Xorg packages to
sup
apport information
** Tags added: apport-collected
** Description changed:
In a recent driver, Nvidia finally added Linux support for render
offload, where most graphics are rendered on the CPU-onboard GPU and
only certain applications are rendered on the discrete Nvidia GPU. I
know that
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1849214/+attachment/5299051/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-435 in
** Also affects: nvidia-graphics-drivers (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-435 in Ubuntu.
https://bugs.launchpad.net/bugs/1849214
Title:
"nvidia
Public bug reported:
I have a Microsoft Surface bluetooth keyboard, and semi-frequently (e.g.
around every 10-15mins) end up with repeated keypresses being made (e.g.
apppt get update).
This seems to happen when the machine is under slight stress, or when a
new notification pops up in gno
I've now been using an Xorg session rather than Wayland and haven't seen
the repeated keys issue. I do get some very nasty screen tearing when
scrolling (e.g. websites) on Xorg however, so ideally I'd like to
continue using Wayland.
Does that mean that this is likely a mutter bug, rather than blue
ubuntu27.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: matt 2519 F pulseaudio
/dev/snd/controlC0: matt 2519 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 7 11:54:57 2019
InstallationDate: Installed on 2019-09-04 (
I went back pretty far, into the 4.x versions, and still had the same
results, so I'm guessing this isn't kernel-related. Any suggestion on
what else to try?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
nelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: matt 2519 F pulseaudio
/dev/snd/controlC0: matt 2519 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date:
Public bug reported:
I have a zfs filesystem containing a single qemu kvm disk image. The vm
has been working normally. The image file is only allocated 10G, however
today I became aware that the file, when examined from the ZFS host
(hypervisor) is reporting an inexplicable, massive file size of
A scrub of the pool detected no issues, no errors.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1766308
Title:
inexplicably large file reported by zfs filesystem
Status in zfs-lin
This has happened to me a couple times, I dont have a clear answer how
to fix it yet, but the dkms install hangs waiting for input at the
secure-boot update screen, but it seems to open in different tty so I
end up having to kill the process to regain control of the terminal. You
can see virtualbox
Confirmed issue on Bionic. Also confirmed the suggested patch in 1661629
#3 fixed the install for me.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1687791
Title:
Install of kdum
What instance type saw this kernel panic?
--
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/1787258
Title:
3.13.0-155.205 Kernel Panic - divide by zero
Status in linux package in Ubuntu:
I've struggled through this several times now. I don't have a definitive
solution but the general routine was something like this. When you asked
to enroll the machine owner key to sign the kernel module there is an
interface that popups up and waits for user input. I tried this in in a
shell-only
Public bug reported:
When booting with ipv6.disable=1, vxlan tunnels will fail to initialize
with the error "vxlan: Cannot bind port 4789, err=-97" which is
EAFNOSUPPORT.
Expected result is that vxlan tunnels work when ipv6 is disabled.
Description:Ubuntu 16.04.4 LTS
Release:16.04
l
** Description changed:
When booting with ipv6.disable=1, vxlan will fail to initialize with the
error "vxlan: Cannot bind port 4789, err=-97" which is EAFNOSUPPORT.
Expected result is that vxlan tunnels work when ipv6 is disabled.
Description: Ubuntu 16.04.4 LTS
Release: 16.
** Patch added:
"0001-vxlan-correctly-handle-ipv6.disable-module-parameter.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771301/+attachment/5139772/+files/0001-vxlan-correctly-handle-ipv6.disable-module-parameter.patch
--
You received this bug notification because you are a me
1. Yes, compression is on for the parent and inherited. The ratio only
shows 1.37x, which seems rather low if a 12T file was all zeros except
for >10G?
root@fusion:~# zfs get all rpool/DATA/fusion/store/vms/plexee | grep comp
rpool/DATA/fusion/store/vms/plexee compressratio 1.37x
Great, thank you. zdb confirms what we already sort of suspected: the
file is ~12T with only 5.5G of real content. I was aware that ZFS
reported on disk size differently, but the fact that this isn't a
feature of compression threw me off in the output.
Object lvl iblk dblk dsize dnsize ls
Yes, please close... thanks again.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1766308
Title:
inexplicably large file reported by zfs filesystem
Status in zfs-linux package in Ub
It's been over a year now and still theres been no reply as to why
Ubuntu won't install on my laptop. Total waste of time.
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
set to regain control of the system and the output doesn't get flushed to
disk), but I did manage to get a photo of some of it (please refer to
attachment).
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/
I did a clean install of BIONIC via ubuntu-18.04.1-server-arm64.iso on
an ARM system and encountered this on first boot. I am happy to send
logs but apport-collect states that I am not the owner
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
>From playing around it appears about 300 seconds after boot.
I was able to recreate this with kernel 4.15.0-29-generic but no longer after
running apt upgrade and rebooting to the 4.15.0-36-generic kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which
Public bug reported:
Description:Ubuntu Cosmic Cuttlefish (development branch)
Release:18.10
4.18.0-8-generic #9-Ubuntu SMP Mon Sep 10 16:12:10 UTC 2018 x86_64
x86_64 x86_64 GNU/Linux
https://bugzilla.redhat.com/show_bug.cgi?id=1608242
Looks like's it's fixed in kernel 4.18.10
This
on reboot.
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu11
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC1: matt 2179 F pulseaudio
+ /dev/snd/controlC0: matt 2179 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelea
r issues this causes is the systemd-udevd hanging on reboot.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: matt 2179 F pulseaudio
/dev/snd/controlC0: matt 2
3bf3e943b8d6005b72c1
Other issues this causes is the systemd-udevd hanging on reboot.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: matt 2179 F pulseaudio
/dev/snd/controlC0
ssues this causes is the systemd-udevd hanging on reboot.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: matt 2179 F pulseaudio
/dev/snd/controlC0: matt 2
Other issues this causes is the systemd-udevd hanging on reboot.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: matt 2179 F pulseaudio
/dev/snd/controlC0: matt 2
ssues this causes is the systemd-udevd hanging on reboot.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: matt 2179 F pulseaudio
/dev/snd/controlC0: matt 2
8d6005b72c1
Other issues this causes is the systemd-udevd hanging on reboot.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: matt 2179 F pulseaudio
/dev/snd/controlC0
72c1
Other issues this causes is the systemd-udevd hanging on reboot.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: matt 2179 F pulseaudio
/dev/snd/controlC0
72c1
Other issues this causes is the systemd-udevd hanging on reboot.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: matt 2179 F pulseaudio
/dev/snd/controlC0
Other issues this causes is the systemd-udevd hanging on reboot.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: matt 2179 F pulseaudio
/dev/snd/controlC0: matt 2
ssues this causes is the systemd-udevd hanging on reboot.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: matt 2179 F pulseaudio
/dev/snd/controlC0: matt 2
Other issues this causes is the systemd-udevd hanging on reboot.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: matt 2179 F pulseaudio
/dev/snd/controlC0: matt 2
72c1
Other issues this causes is the systemd-udevd hanging on reboot.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: matt 2179 F pulseaudio
/dev/snd/controlC0
r issues this causes is the systemd-udevd hanging on reboot.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: matt 2179 F pulseaudio
/dev/snd/controlC0: matt 2
** Attachment added: "stack-trace.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803929/+attachment/5214086/+files/stack-trace.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/
Public bug reported:
lsb_release -rd
Description:Ubuntu 16.04.5 LTS
Release:16.04
uname -a
Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
Steps (1) to reproduce:
1) Plug in a USB3 hard drive.
2) Right click on launcher ico
't get flushed to
disk), but I did manage to get a photo of some of it (please refer to
attachment).
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio
/dev/snd/cont
t flushed to
disk), but I did manage to get a photo of some of it (please refer to
attachment).
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio
/dev/snd/controlC1:
untu2.18
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio
+ /dev/snd/controlC1: matt 2754 F pulseaudio
+ /dev/snd/controlC0: matt 2754 F pulseaudio
+ CurrentDesktop: Unity
+ DistroRelease: Ubu
output doesn't get flushed to
disk), but I did manage to get a photo of some of it (please refer to
attachment).
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio
hed to
disk), but I did manage to get a photo of some of it (please refer to
attachment).
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio
/dev/snd/controlC1: matt
't get flushed to
disk), but I did manage to get a photo of some of it (please refer to
attachment).
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio
/dev/snd/cont
't get flushed to
disk), but I did manage to get a photo of some of it (please refer to
attachment).
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio
't get flushed to
disk), but I did manage to get a photo of some of it (please refer to
attachment).
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio
/dev/snd/cont
hed to
disk), but I did manage to get a photo of some of it (please refer to
attachment).
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio
/dev/snd/controlC1: matt
hed to
disk), but I did manage to get a photo of some of it (please refer to
attachment).
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio
/dev/snd/controlC1: matt
hed to
disk), but I did manage to get a photo of some of it (please refer to
attachment).
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio
/dev/snd/controlC1: matt
't get flushed to
disk), but I did manage to get a photo of some of it (please refer to
attachment).
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio
/dev/snd/cont
a hard
reset to regain control of the system and the output doesn't get flushed to
disk), but I did manage to get a photo of some of it (please refer to
attachment).
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
t flushed to
disk), but I did manage to get a photo of some of it (please refer to
attachment).
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio
/dev/snd/controlC1:
hed to
disk), but I did manage to get a photo of some of it (please refer to
attachment).
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio
/dev/snd/controlC1: matt
se refer to
attachment).
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio
/dev/snd/controlC1: matt 2754 F pulseaudio
/dev/snd/controlC0: matt
4
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio
/dev/snd/controlC1: matt 2754 F pulseaudio
/dev/snd/controlC0: matt 2754 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
EcryptfsInUse: Yes
ortVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: matt 2754 F...m pulseaudio
/dev/snd/controlC1: matt 2754 F pulseaudio
/dev/snd/controlC0: matt 2754 F pulseaudio
CurrentDesktop:
I think I see the same bug on Dell Inc. Latitude 7390 2-in-1/0YNG30,
BIOS 1.10.0 07/04/2019
Distributor ID: Pop
Description:Pop!_OS 20.04 LTS
Release:20.04
Codename: focal
Observed on the latest four kernel versions:
vmlinuz-5.4.0-7618-generic
vmlinuz-5.4.0-7629-generic
vmlinuz-
Thank you for fixing this bug. Installing mutter 3.36.4-0ubuntu0.20.04.1
and libmutter 3.36.4-0ubuntu0.20.04.1 from focal-proposed has resolved
this issue for me.
Note: The updated libmutter from focal-proposed also had to be
explicitly installed by me, as it was not automatically pulled in when
u
: Ubuntu 5.0.0-27.28-generic 5.0.21
Uname: Linux 5.0.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: matt 2519 F pulseaudio
/dev/
I apologize for my ignorance, but now that tall these check ins have
occurred, how do I know when an installable package has been built and
is available in the various repos?
And thank you @inaddy for the diligence getting this one resolved.
--
You received this bug notification because you are
Thanks, and will notifications appear here in the bug during these
stages?
--
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/1569925
Title:
Shutdown hang on 16.04 with iscsi targets
Status
The issue is with suspend. It suspends perfectly if I just boot up and
immediately try it. If I work on a project in vs code for a couple
hours, it almost always freezes.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
htt
Yes, suspend had no issues on 16.10.
--
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/1740175
Title:
Ubuntu 17.10 not resuming from suspend, freezing on shut down
Status in linux package
I can confirm that booting with the 4.10.0-36-generic_4.10.0-36.40
kernel from your link cured the slow graphics fault, everything ran
smooth, back to normal. I did lose wifi though :-)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
@Joseph: Can also confirm that 4.10.0-35 fixed it.
--
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/1723174
Title:
Intel graphics problems on kernel 4.10.0-37-generic
Status in linux pack
I can confirm that linux-image-4.10.0-36-generic Commit111757e7b6de9
fixed the problem. Wifi not working though.
--
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/1723174
Title:
Intel graph
I can confirm that linux-image-4.10.0-36-generic Commit
ae95914a9a3cd5060dcd1d0a9d02906f97bc56d1 fixed the problem. Wifi not
working though.
--
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/1
I can confirm that linux-image-4.10.0-37-generic Commit
8b1a7b0607a840e73e9b6fd15cc01d800742fe43 fixed the problem. Wifi not
working though.
--
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/1
linux-image-4.10.0-37-generic Commit
b1943b80d393d40a75c7fd0679f51d6f998d28d5 fixed the problem. Wifi not
working again though.
--
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/1723174
Title
This bug is also occurring for me when installing nvidia-387 off
Nvidia's 16.04 repository when using 4.13.0-26-generic. Attached is
/var/lib/dkms/nvidia-387/387.26/build/make.log.
** Attachment added: "make.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742302/+attachment/5034844/
I also installed and booted 4.15-rc7 and attempted to install nvidia-387
and got another crash in the DKMS build process.
However I installed nvidia-384 (this would be the just-released 384.111)
on 4.13.0-26-generic and it works fine.
--
You received this bug notification because you are a membe
g if Intel graphics card available...
• checking for i915 module in /sys/module
• i915 module found
Checking if Intel graphics card available... OK
Retrieving information from 01.org...
...
And with this -35 kernel the video is smooth and fast.
Matt
--
You received this bug notification because
Installed linux-headers...all, linux-headers...generic amd64, image
amd64 and image-extra using dpgk -i *.deb this time instead of using the
software centre I used to install the previous images. Started Ubuntu
with 4.10.0-36-generic. This slow video problem is now present. But wifi
now works.
--
101 - 200 of 409 matches
Mail list logo
