ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Uname: Linux 3.11.0-13-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: imac 2900 F pulseaudio
/dev/snd/controlC0: imac
[ 1645.092461] systemd-udevd[4661]: Failed to apply ACL on
/dev/bus/usb/002/005: No such file or directory
The udev ACL fails because the device is already gone; Nowhere in lsusb
either.
imac@imachp:~$ lsusb
Bus 002 Device 003: ID 1bcf:2805 Sunplus Innovation Technology Inc.
Bus 002 Device 002: ID
Updated here https://lkml.org/lkml/2014/5/22/685
--
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/1089768
Title:
Marvell Sata controller and AMD-Vi problems
Status in linux package in
Looks like there is a patch here: https://lkml.org/lkml/2013/3/7/582
--
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/1089768
Title:
Marvell Sata controller and AMD-Vi problems
Status in
Can the maintainers please have a look at the following for rtl8812au
4.3.20,
https://github.com/diederikdehaas/rtl8812AU/tree/driver-4.3.20
It is working on my Ubuntu 16.10 and resolves the build issues with the
current 4.3.14 dkms source.
root@dottodesk:/usr/src# uname -a
Linux dottodesk
In my case, I am running Ubuntu 22.04 uptodate.
This trackpad bug has been around a while, and due to the slight process
naming differences between platforms, it can be hard to link them
together.
For myself, this happens on my XPS 13 9385, after coming out of sleep,
with a similarly named
Backporting to LTS is a good idea IMHO. A few additional use cases to
consider
- Users on the threshold who experience slight initrd image growth due
to any module update
- Users who thought they might be able to continue just using older
images may fail to recognize grub will eventually remove
My XPS 13 9380 (no luks) also triggers this on 5.19 after the 22.10
upgrade; I can see the initrd is about 7% bigger in 22.10 over 22.04.
-rw-r--r-- 1 root root 111203941 Oct 30 18:16 initrd.img-5.15.0-52-generic
-rw-r--r-- 1 root root 120222346 Oct 31 21:39 initrd.img-5.19.0-23-generic
#103
-> If an user somehow met this issue, then the system is not able to
boot.
It can boot, if it did previously, and this issue will get fixed pretty
quick IMHO in the updates repository given it impacts current 20.04,
22.04 and 22.10.
Here is just the workaround part, for current 22.10 or 22.04 to
9 matches
Mail list logo
