Great, thanks!
--
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/2080192
Title:
High fidelity playback won't be enabled for bluetooth headset unless
reconnected through settings
Status i
Removing pairing and adding it again does not solve the issue.
--
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/2080192
Title:
High fidelity playback won't be enabled for bluetooth headset
** Attachment added: "Screenshot from 2024-09-10 08-28-45.png"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2080192/+attachment/5815064/+files/Screenshot%20from%202024-09-10%2008-28-45.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
Public bug reported:
When connecting my Sony WH-XB900N bluetooth headset, it will only
connect as a handsfree set using the low quality mSBC codec unless I
manually open the device in the bluetooth settings and toggle the
"Connection" switch off and on again. It then will connect as a headset
with
Confirmed! Finally. With the latest HWE:
$ apt show linux-image-5.11.0-37-generic
Package: linux-image-5.11.0-37-generic
Version: 5.11.0-37.41~20.04.2
...
No errors or warnings in dmesg or journalctl -b seen on my statem
anymore.
Motherboard: ASUS PRIME X570-PRO (latest BIOS v 4021)
CPU: Ryzen
Confirmed. Just updated and same.
Can you backport the fix to the 20.04 HWE kernel? I mean that's the one
Canonical recommends has as first choice if downloading Ubuntu from
ubuntu.com, for years now. And they've become more stable in my
experience than the ones between LTS versions, which is good
And will that kernel come to the Ubuntu 20.04 LTS HWE stack, say in
20.04.4? Kinda need to use LTS versions, us that need that stability at
least.
Not really interested in fixes for 21.10 or something... Focal.
--
You received this bug notification because you are a member of Kernel
Packages, wh
To be clear this issue started with Kernel 5.8.0-63 NOT 5.11 (on Focal /
20.04 HWE LTS)
Well Ubuntu Kernel Bot, that's exactly what I did in comment #14
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937897/comments/14
Latest 5.13 kernel in -prosed on Focal (20.04.3) gets the same gpio
err
** Tags removed: verification-needed-focal
** Tags added: verification-failed-focal
--
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/1937897
Title:
GPIO error logs in start and dmesg after
Added tag 'verification-failed-hirsute'. Enabled proposed and installed
package 'linux-image-5.13.0-14-generic' version '5.13.0-14.14~20.04.4'
on my 20.04.3 LTS, and still get in dmesg:
[1.228729] gpio gpiochip1: (gpio_aaeon): tried to insert a GPIO chip with
zero lines
[1.228732] gpiochi
--
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/1929504
Title:
Add support for IO functions of AAEON devices
Status in linux package in Ubuntu:
Fix Released
Status in linux source packa
OK, but don't try to load the gpio-aaeon module on PCs that, if simply
one tries to load it manually, it simply says that no such device
exists... It shows twice in the boot log (dmesg + journalctl -b) but
even worse also on the monitors, although GRUB has "quiet" specified (no
splash).
Worst of a
Well OK there is a module with that name, however I did blacklist it and
same error still occurs. It happens very early in the boot process. Now
maybe it tries to load gpio-aaeon, but still early to load modules I
would say, it's still doing say GRUB kernel parameters like fsck ones.
Now I have co
No, I can't, because there isn't a single module loaded with even the
name "gpio" in it.
So running: $ lsmod|grep gpio == No result
It's in the kernel, not a module. I reverted to the GA kernel and
although with that I've had some issue with on headless *Intel* NUC
running Virtual Machines that u
EDIT: To clarify both times these lines come they refer to "gpiochip1"
(so not 2 different ones).
I started getting the same 3 lines of errors TWICE at boot, with the now
latest official 5.8 HWE kernel. Without "splash", just "quiet" set for
GRUB it also shows on my monitors when booting. Honestly
FWIW, I do this dance after boot and the touchpad works...
➜ ~ sudo modprobe psmouse
[sudo] passord for ole:
➜ ~ sudo rmmod psmouse
➜ ~ sudo modprobe psmouse
Sincerely,
Ole
ons. 23. sep. 2020 kl. 23:29 skrev Ole Morten Heggebakken Amundsen <
ole.morten.amund...@gmail.com>:
> Th
> [12.196] (II) config/udev: Adding input device Synaptics TM3418-002
> (/dev/input/mouse0)
> [34.235] (II) event7 - Synaptics TM3418-002: device removed
>
> ProblemType: Bug
> DistroRelease: Ubuntu 20.04
> Package: linux-image-5.4.0-47-generic 5.4.0-47.51
&g
7.51
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: ole 2093 F pulse
Hi, I have got basically the same machine, but the 14 inch version. My touchpad
randomly works or not (about 50:50), but its behavior only changes after a
second boot. If it does not work, I do constantly get the following kernel
errors:
i2c_designware AMDI0010:00: controller timed out
Also, the
Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ole2200 F pulseaudio
/dev/snd/controlC0: ole2200 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon J
Might be connected to this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776266
Might a hardware issue. Sometimes the cable that connects the keyboard
and touchpad to the mainboard is flaky. This causes the devices to stop
working (see mentioned bug) or wake up the laptop (this bug).
lspci -vvnn:
04:00.0 Non-Volatile memory controller [0108]: Sandisk Corp WD Black NVMe SSD
[15b7:5001] (prog-if 02 [NVM Express])
Subsystem: Marvell Technology Group Ltd. WD Black NVMe SSD [1b4b:1093]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- S
I should probably mention that while it is installed in my laptop it is
not currently being used as I had to revert to using an ordinary HDD.
--
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/
lshw output:
*-storage
description: Non-Volatile memory controller
product: Sandisk Corp
vendor: Sandisk Corp
physical id: 0
bus info: pci@:04:00.0
version: 00
width: 64 bits
I have the WD Black 256 Gb drive.
--
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/1746340
Title:
Samsung SSD corruption (fsck needed)
Status in linux package in Ubuntu:
Confirmed
Bug
I may try that. Are we sure it's a kernel bug though? I can't remember
having this problem when I used Solus OS for a while. But I may not have
used for long enough since I discovered it didn't support Jack2 and was
pretty much unusable to me.
--
You received this bug notification because you are
Hi Lucas! Thanks for the reply. No, I had no problems during
installation. The computer just shuts down at random intervals to a
black screen with all kinds of EXT4-fs errors and reports that the file
system is read only. Often the disk isn't even recognized at reboot, so
I have to boot into a live
I have this bug (MSI laptop, Ubuntu Studio 18.04) and it's getting quite
annoying to be honest. If there's anything I can do to help remedy the
situation within reasonable time (I'm about to reinstall) then let me
know.
--
You received this bug notification because you are a member of Kernel
Pack
tu7.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ole2200 F pulseaudio
/dev/snd/controlC0: ole2200 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun 11 19:25:07 2018
InstallationDate: Installed on 2018-06-01 (10 day
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-22-generic 4.15.0-22.24
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMM
tu7.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ole2200 F pulseaudio
/dev/snd/controlC0: ole2200 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun 11 19:25:07 2018
InstallationDate: Installed on 2018-06-0
tu7.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ole2200 F pulseaudio
/dev/snd/controlC0: ole2200 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun 11 19:25:07 2018
InstallationDate: Installed on 2018-06-01 (10 day
Public bug reported:
After going into suspend (via command line or lid close), the MacBook
Pro (early 2015) wakes up immediately again. Same for hibernation.
Running Ubuntu 18.04.
extract from dmesg for a lid-close -> suspend -> wake-up -> lid-open
cycle:
[0.00] Linux version 4.15.0-22-g
Not sure which version this was fixed in (maybe around 4.11?), but I
updated my kernel to 4.13.16 in Ubuntu 16.04 and the touchpad is
recognized just fine now.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
Hi Matt,
did you try the workaround that I suggested in the bugreport? Does it work? I
still need to do it on my machine, but it mitigates the problem.
Cheers,
Nils
> Gesendet: Dienstag, 13. Januar 2015 um 08:50 Uhr
> Von: "Matt Hanyok" <1318...@bugs.launchpad.net>
> An: nol...@gmx.de
> Betreff:
I found the following workaround:
as root:
echo "min_power" >
/sys/class/scsi_host/host4/link_power_management_policy
where host4 correspnds to my ata5 in the error message. Now the error
messages have stopped. I hope this helps with debugging
--
You received this bug notification because you
I just installed a fresh Xubuntu 14.04 on an iMac with Fusion drive. I
split the Fusion drive to install the ubuntu on the SSD. I now get a lot
of very similar errors:
[332951.343902] ata5: irq_stat 0x0040, PHY RDY changed
[332951.343908] ata5: SError: { PHYRdyChg }
[332951.343916] ata5: hard
37 matches
Mail list logo
