-0ubuntu17.6
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: robin 2411 F pulseaudio
/dev/snd/controlC1: robin 2411 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xe858 irq 44'
Mixer name
*** This bug is a duplicate of bug 1189721 ***
https://bugs.launchpad.net/bugs/1189721
** This bug has been marked a duplicate of bug 1189721
Ralink RT3290 needs bluetooth driver
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
*** This bug is a duplicate of bug 1189721 ***
https://bugs.launchpad.net/bugs/1189721
For the avoidance of anyone's doubt, this bug is functionally a
duplicate of bug #1189721. The reason for the problem as reported on
bug 1234541 is that there is *no* driver to enable the bluetooth
12.04 to 14.04 for the driver no longer to be effective, as one
understands it. Had the manufacturer updated the driver, or someone else
taken over maintenance (with or without manufacturer's sponsorship),
then this frustrating problem would not have arisen.
Cheers,
Robin
PS: It wasn't really
for the driver no longer to be effective, as one
understands it. Had the manufacturer updated the driver, or someone else
taken over maintenance (with or without manufacturer's sponsorship),
then this frustrating problem would not have arisen.
Cheers,
Robin
PS: It wasn't really necessary
The description in #5 is not a fix, but rather a hack, which will have to be
repeated for every kernel update. A true fix would involve:
a) amending the btusb file
b) including the fully BT capable firmware in a package
If only a) is done, that would be a big improvement!
Please note that 14.04
Public bug reported:
dmesg | tail -n 35 |less
Extract:
[ 337.978401] xhci_hcd :00:10.0: xHCI xhci_drop_endpoint called with
disabled ep 880414902d90
[ 337.978405] xhci_hcd :00:10.0: xHCI xhci_drop_endpoint called with
disabled ep 880416e56b40
[ 337.979961] cdc_acm 6-2.3:1.1:
Commenting out blacklist i2c_i801 did end with mouse not working at all
after wakeup but adding psmouse.synaptics_intertouch=0 to grub did solve
the issue. I got an L440. Ubuntu 18.04 4.19rc1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
@whitequark I was struggling to get stuff to work with the Apple
Thunderbolt 3 to 2 adapter, but when I replaced it with the Startech
Thunderbolt 3 to 2 I got it working. Read about other's recommending it
online as well.
--
You received this bug notification because you are a member of Kernel
As suggested in #3 above, this solution may work:
The clean solution to this issue is to install libjack-jackd2-dev
*before* installing portaudio19-dev.
I have a note on this, available on request.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Thanks for your comments
@Hui Wang: The additional line worked. Following your steps the bug could no
longer be reproduced with kernel 5.1.5-050105. Thanks a lot. Would it be
suitable to apply these changes as default or to propose them commented out in
the config file?
@Kai-Heng Feng: Your
I installed your kernel and commented out the previous manual configuration.
All is working fine and the speakers are working after suspend, too. So the bug
can't be reproduced.
Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Package changed: ubuntu => zfs-linux (Ubuntu)
--
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/1973463
Title:
ZFS kernel null pointer dereference
Status in zfs-linux package in
Sorry, this is not a reliably reproducible bug so I won't be able to
provide any more logs. Feel free to close if this this report is not
useful
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug is still very much a thing. A quick search will show plenty of
recentish talk on forums of other distros.
On my laptop it affects both 20 LTS and the latest 22.10.
Have tried everything. Disabling wifi power management. Limiting the
band to 2.4khz (supposedly more stable). Upgrading the
Interesting. Yes `pcie_aspm=off` is already in the grub parameters but
not `pcie_port_pm=off`. I will add that now, wait for the daily crash
and then report back in due course.
Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Crashed. :(
$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-5.15.0-56-generic root=/dev/mapper/vgubuntu-root ro text
pcie_aspm=off pcie_port_pm=off
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hello thedoctar.
As mentioned, I had 22.10 installed with latest repo-provided firmware.
That's pretty recent isn't it?
I also tried a surgical downgrade of the ath10k firmware to a version
corresponding to 20 LTS. Crashes continued.
I tried removing the firmware6.bin file which forced "API5"
Ideas, anyone? (Driving me crazy - 5 crashes this morning.)
This is basically a virgin Ubuntu 20 LTS. My laptop had no problems with
20 LTS until about a year ago. To exclude hardware failure as the cause,
my idea is to get the software back to the state it was in a year ago.
Is that reasonable?
But how would the live CD change anything? I'm on exactly the same
version as the live CD right now (20.4.5).
What I *know* is that my system was stable on 20.4.1 from two years ago,
i.e. that version of the kernel, modules, and firmware.
So how would I go about reverting to it (and blocking
Thanks. So I installed 18 LTS again. A major PITA, but I used 18 LTS on
this laptop for 2 full years without a problem. Always fully upgraded,
so with all the standard permutations of kernel, modules and firmware,
on lots of different wifi networks. There was never a single issue. Nor
under 16.10
$ sudo lshw -C Network
*-network
description: Wireless interface
product: QCA9377 802.11ac Wireless Network Adapter
vendor: Qualcomm Atheros
physical id: 0
bus info: pci@:01:00.0
logical name: wlp1s0
version: 31
serial:
@kaihengfeng I try to use only the most vanilla setup, so yes, it has
happened with all the mainline Ubuntu kernels coming from 20 LTS
upgrades over the last year and also 22.10.
Suspend is disabled, I guess by kernel parameter `pcie_aspm=off`, by
`HandleLidSwitch=ignore` in
Just the usual "failed to wake target", sometimes accompanied by
"firmware crashed!", but always requiring a full reboot to fix.
BUT occasionally it even "sleeps through" the reboot and requires a
second reboot! In fact this was what happened last time, yesterday.
Here's the dmesg:
[
I think it's likely that firefox crashing on bumble/whatsapp is a red
herring, a coincidence. As Donald reports, his setup crashes on any new
tabs.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I'm on kernel 6.0.7, all appears well so far.
--
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/1995238
Title:
snaps randomly crash after some time
Status in snapd:
Invalid
Status in
-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: robin 2394 F pulseaudio
CurrentDesktop: Unity
Date: Thu Oct 27 18:46:42 2016
HibernationDevice: RESUME=UUID=ad90ea5b-2c52-473c-8431-7a785290e6d4
InstallationDate: Installed
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: robin 2394 F pulseaudio
CurrentDesktop: Unity
Date: Thu Oct 27 18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: robin 2394 F pulseaudio
CurrentDesktop: Unity
Date: Thu Oct 27 18:46:42 2016
HibernationDevice: RESUME=UUID=ad90ea5b-2c52-473c-8431-7a785290e6d4
InstallationDate: Installed on 2016-10-25 (2 days ago
Following the instructions here: http://askubuntu.com/questions/833322
/pair-bose-quietcomfort-35-with-ubuntu-16-04-over-bluetooth I managed to
make it pair and appear as an audio device.
While playback technically worked, it wasn't useable as it came across
as though there wasn't enough
This is ubuntu desktop. I found that if I did:
sudo hciconfig hci0 lp HOLD,SNIFF
while everything was disconnected, then the audio started working
properly.
Now I'm back here because after a reboot it wouldn't connect at all, so
I guess I need to fix the pairing or something.
--
You received
I have also coruppted bios on Lenovo y50-70. I cant do any chnages. Do
you think that will be a software solution ? I hope i wont to change MB.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Peter Smith - I had the same experience of trying the 4.15.0-33 and it not
working for me.
** Try 4.15.0.23 if you would like to be on the 4.15 kernel **
Background:
In my case I am running Mint, but same Ubuntu kernels. It is a desktop PC which
is not often suspended so I noticed the problem
Had access to another Ideapad with touchpad MSFT0001:00 04F3:3140
installed. Kernel 5.10.2-051002-generic #202012210832 did not work out
of the box but in combination with #322 it worked so i can confirm, too.
--
You received this bug notification because you are a member of Kernel
Packages,
@wangjun (biggerchina) i can confirm that #311 is working without any
workarounds when applied on 5.10.3 with touchpad MSFT0001:00 04F3:3140
and Ubuntu 20.04, thanks!
If anyone on a Debian based system is interested: i've uploaded the
patched version as .deb-packages here
I'm also on 20.04 and my network connection stopped working after an
update today. I have a Broadcom BCM4360.
I got things working again by following the steps shared by rafae-s
(thank you!), but I expect that other 20.04 users will come across the
same problem in the next couple of days.
Does a
For me it's a dongle (https://www.amazon.de/Mpow-Bluetooth-Empf%C3
%A4nger-Lautsprecher-
kompatibel/dp/B087JRFGV7?pd_rd_w=YmEc6_rd_p=8d2a1a06-f0ba-4603-bd06-75edf607bd62_rd_r=7PQ125F33S6FJFDZX9SK_rd_r
=4484adca-29c6-4c15-b00d-
b94cc61893bb_rd_wg=rSu7g_rd_i=B087JRFGV7_=pd_bap_m_rp_1_sc)
and it's
Could you try to boot in recovery mode and then resume the normal boot
process? I think i have the MSFT0001:00 06CB:7F28 touchpad installed but
i'll check these days.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I'm on Ubuntu 20.04 with kernel 5.10.1 (https://kernel.ubuntu.com
/~kernel-ppa/mainline/v5.10.1/) and the touchpad is working on my Lenovo
Legion 5. Thanks for that guys :-)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@Piotr Tomaszewski (nfm886) i just installed headers (all), image
(generic) and modules (generic) from https://kernel.ubuntu.com/~kernel-
ppa/mainline/v5.10.1/amd64/ via 'dpkg -i *.deb', rebooted with new
kernel 5.10.1 and everything worked. So no special config or parameter
tweaking was necessary
@Piotr Tomaszewski (nfm886) can confirm my touchpad is the MSFT0001:00
06CB:7F28. I booted kernel 5.10.1 into recovery and then resumed regular
boot and my touchpad works.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@Piotr Tomaszewski (nfm886) according to #109 it seems like you have the
"Elan" touchpad (mine is the "Synaptic" one) so it might behave a little
different?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
sudo dpkg --configure -a
Setting up libaccinj64-10.1:amd64 (10.1.243-3) ...
dpkg: dependency problems prevent configuration of libcuinj64-10.1:amd64:
libcuinj64-10.1:amd64 depends on libcuda1 (>= 418.39) | libnvidia-tesla-cuda1
(>= 418.39) | libcuda.so.1 (>= 418.39) |
If you like you can dowload the patched 5.10.3 kernel from the link i
posted in #332. Just download the two files and install them via dpkg -i
*.deb
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Mint 17.1 does not solve the problem. It is extremely disapointing that
this issue has not been solved. Why does 16 work and 17 does not?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Hey!
I bought a bluetooth headphone, but the volume, next and previous track
buttons don't work with my Ubuntu Phone, because it doesn't support
AVRCP. So please implement this feature. :)
** Affects: bluez (Ubuntu)
Importance: Undecided
Status: New
--
You
Public bug reported:
One notices *.old-dkms files being left behind still sitting on the disk
after purging the related kernel. This can cause /boot to become full,
and when it gets really bad, even sudo apt-get autoremove won't fix the
problem - only deleting the old-dkms files manually solves
Which upstream commit actually fixed this problem?
--
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/1467867
Title:
USB devices found but not working
Status in linux package in Ubuntu:
ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
Uname: Linux 3.19.0-28-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: robin 1800 F pulseaudio
/dev/snd/controlC1: robin 1800 F
I can reproduce this on BQ Aquaris E4.5 - krillin - rc-proposed r277
(released today) and this bug is really annoying. :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1488170
Title:
I can confirm that this is still an issue in Ubuntu 14.04.4. I ran into
this problem trying to backup a server hosting lxc containers, some of
them using overlayfs as the root fs. When the containers are running
(and therefore overlayfs is mounted) lvcreate -s hangs forever. The
debug output is:
Did something change with this? Because I can't reproduce this any more
on my bq Aquaris E4.5 phone with OTA-11. With OTA-10.1 this happened
every time.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
Public bug reported:
With my brand new Dell XPS 13 9350 and Ubuntu 15.10. The graphical
"reboot" and "shut down" buttons don't do anything, and from the CLI I
get:
$ reboot
Failed to execute operation: Transaction is destructive.
I imagine it's associated with closing the lid to suspend because
apport information
** Tags added: apport-collected wily
** Description changed:
With my brand new Dell XPS 13 9350 and Ubuntu 15.10. The graphical
"reboot" and "shut down" buttons don't do anything, and from the CLI I
get:
$ reboot
Failed to execute operation: Transaction is
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1536249/+attachment/4553474/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
It says "not installed" 'cos I'm using a kernel from here:
http://askubuntu.com/questions/709794/dell-xps-13-9350-compatibility -
to get my wifi to work. Does this make this bug invalid? Maybe I should
file a bug about wireless not working with the ubuntu kernel?
** Description changed:
With
I took a different approach to getting my mouse working: I installed
blueman and used that to configure it. I guess it enables experimental
features itself.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
We have been seeing this issue intermittently on a set of servers that
were running Ubuntu 15.10 and then 16.04. After overriding that udev vm
hotadd rule as suggested above a couple weeks ago, the issue has yet to
return (not a conclusive result, but so far so good).
--
You received this bug
To add - these servers are all built on the official Ubuntu Amazon EC2
AMIs of the 'ebs-ssd' variety.
--
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/1518457
Title:
kswapd0 100% CPU
4.15.18
Uname: Linux 4.15.0-91-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: robin 1736 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 2 17:01:25 2020
InstallationDate
ACCESS COMMAND
/dev/snd/controlC0: robin 1736 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 2 17:01:25 2020
InstallationDate: Installed on 2018-10-11 (539 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Hewlett-
I had similar problems with this too.
The .ko that is delivered with 21.10 gives me the same output as above.
I downloaded the firmware from ASIX and tried to compile it.
That didn't work because 'usbnet_get_stats64' (line 1030) no longer exist in
kernel 5.11 and up.
I had to change it out for
22.04
Package: linux-image-5.15.0-52-generic 5.15.0-52.58
ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
Uname: Linux 5.15.0-50-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: robin 4304 F
5.15.0-52.58
ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
Uname: Linux 5.15.0-50-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: robin 4304 F pulseaudio
/dev/snd
/controlC1: robin 4304 F pulseaudio
/dev/snd/controlC0: robin 4304 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 19 14:53:25 2022
InstallationDate: Installed on 2022-03-17 (216 days ago)
InstallationMedia: Ubuntu 22.04 LTS "
Package: linux-image-5.15.0-52-generic 5.15.0-52.58
ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
Uname: Linux 5.15.0-50-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: robin
Issue re-reproduced on Ubuntu 22.04 as well, same laptop model (LG Gram
16Z90Q).
--
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/1987829
Title:
LG Gram 12gen high CPU use when USB-C/TB
Not only an Ubuntu bug, it also affects Fedora with similar symptoms.
Also, this happens when the device connected to USBC is a charger; and it
appears to stop once fully charged.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Public bug reported:
I have nvidia drivers to use the secondary GPU. I've notice that,
probably due to kernel upgrades, the module doesn't get rebuilt for the
new kernel. The "additional drivers" tool shows it as being installed
(see screenshot.)
$ lsmod | grep nvi
$
$ nvidia-smi
NVIDIA-SMI has
/dev/snd/controlC1: robin 4304 F pulseaudio
/dev/snd/controlC0: robin 4304 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 19 14:53:25 2022
InstallationDate: Installed on 2022-03-17 (216 days ago)
InstallationMedia: Ubuntu 22.04
-generic 5.15.0-52.58
ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
Uname: Linux 5.15.0-50-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: robin 4304 F pulseaudio
/dev/snd
@kaihengfeng
I gave latest mainline a try on my Fedora, installed through copr according to
this doc: https://fedoraproject.org/wiki/Kernel_Vanilla_Repositories
It's kernel 6.3 instead of 6.2, but I would assume it contains changes from 6.2.
No luck, still same symptoms.
# uname -a
Linux
I would gladly answer #20 @kaihengfeng but I don't have nor want Windows
on this professional machine used for sysadmin work.
Since this appears to be a global kernel issue and I didn't find it on the
Linux kernel Bugzilla, I have forwarded the issue:
: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: robin 4304 F pulseaudio
/dev/snd/controlC0: robin 4304 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 19 14:53:25
Public bug reported:
apport detected this error on a fresh boot.
ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-19-generic 3.13.0-19.40
ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
Uname: Linux 3.13.0-19-generic x86_64
NonfreeKernelModules: nvidia
I'm now running 15.04, so the bug no longer applies. I've marked it as
invalid.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I got a similiar model, the ASUS ROG GL552VW, and I have exactly the
same problem. The touchpad does not work when I boot Xubuntu, but my
gaming mouse that I got with this laptop does seem to work.
I will gladly help you with giving detailed information about this bug,
but I do not know what kind
TL;DR: pass '-vga none' with -nographic, or redirect the screen
somewhere!
I ended up digging into this after it was mentioned by smoser. The bug
is invalid because of a bad assumption in the QEMU inputs. smoser's
workaround of usb=off removes USB as a workaround.
The kernel, OpenFirmware, and
Will new media be available w/ this fix in place?
I ask because running "dkms status" or any dkms command presently
triggers this bug for me, and the only way forward I can see to being
able to fix that system is new media w/ a patched kernel.
--
You received this bug notification because you
79 matches
Mail list logo
