For some reason, killing the bluetoothd process just worked today unlike
previous attempts in the past days. The problem of the headset loosing
connection during a meeting, blocking the bluetooth process and settings
interface, still occurs requiring a restart of the bluetooth service and
the
apport information
** Attachment added: "syslog.txt"
https://bugs.launchpad.net/bugs/1910405/+attachment/5451733/+files/syslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1910405/+attachment/5451729/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1910405/+attachment/5451725/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1910405/+attachment/5451730/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "getfacl.txt"
https://bugs.launchpad.net/bugs/1910405/+attachment/5451731/+files/getfacl.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "rfkill.txt"
https://bugs.launchpad.net/bugs/1910405/+attachment/5451732/+files/rfkill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1910405/+attachment/5451722/+files/Dependencies.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1910405/+attachment/5451723/+files/Lspci.txt
--
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/1910405
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1910405/+attachment/5451727/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1910405/+attachment/5451724/+files/Lsusb.txt
--
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/1910405
apport information
** Tags added: apport-collected
** Description changed:
Hi,
When having a bluetooth headphone (JBL Live) connected using the A2DP
pulseaudio sink, the output sound suddenly stops during a music
streaming of videocall session. Sometimes just disconnecting and
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1910405/+attachment/5451728/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1910405/+attachment/5451726/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
Public bug reported:
Hi,
When having a bluetooth headphone (JBL Live) connected using the A2DP
pulseaudio sink, the output sound suddenly stops during a music
streaming of videocall session. Sometimes just disconnecting and
reconnecting the headphone works, but some times reconnection is not
I'm sorry, the apport-collect comment also results in a hanging process.
See this bug:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1910768
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
The problem is back. This time I let the restart process wait for
several minutes. See this output.
peddecke@omer:~$ sudo service bluetooth restart
Job for bluetooth.service failed because the control process exited with error
code.
See "systemctl status bluetooth.service" and "journalctl -xe"
Hi Daniel et al,
Happy new year if you're already in the new year!
Yesterday, I got the same issue: poor resolution with the (new) DP
cable. Unplugging and reconnection without success.
However, just unplugging and inserting the cable in another port did
some magic and brought the full
Hi Daniel et all,
Only a few days after the previous post, the problem got worse again: after a
reboot I get a poor resolution but see the full 4K resolution available in the
settings. However, after selecting this one, the poor resolution stays and the
4K disappears. The new cable can't be
Hi Daniel et al,
After a few days of working in the full resolution (even after
hibernating and display swapping) today a resume from suspend again
resulted in a poor resolution on my 4K screen. Disconnecting, swapping
cables, rebooting,... didn't solve the issue. I'm stuck in the poor
resolution
Hi Daniel,
I replaced the DP cable. After inserting the cable, the full resolution was
immediately back available. However, the problem/bug still remains: after a
suspend, the screen only gives a poor resolution and the full resolution is not
available. After a reboot, the full resolution is
Hi Daniel,
I just tested with the new kernel:
$ uname -a
Linux omer 6.1.0-060100rc5drmtip20221118-generic #202211180211 SMP
PREEMPT_DYNAMIC Fri Nov 18 03:02:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
But still the same issue. The cable should be OK, as it didn't change
since the time it was
Thanks Daniel,
As I currently have a correct resolution setting at work (see #2)
without any hardware replacement, I don't think this is a hardware
(cable) problem. I'll test this evening at home again, as well as with a
new kernel.
--
You received this bug notification because you are a member
OK, since the upgrade to kernel 6.1 I cannot use the external monitors
at work (through the HP DisplayLink device) anymore. I reinstalled the
DisplayLink driver without success.
$ sudo get-edid | parse-edid
This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
No
Hi Daniel et al,
The past months I could get the full resolution back by waiting a longer
time before inserting the DP cable. However, since the installation of a
bunch of updates last week, this doesn't work anymore. I stay stuck in
the poor resolution. The cables are brand new and were working
25 matches
Mail list logo
