[Kernel-packages] [Bug 1972831] Re: Can pair but cannot connect to bluetooth headphones Sennheiser Momentum 3

2022-05-10 Thread mastier1
That was after upgrade from Focal to Jammy

-- 
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/1972831

Title:
  Can pair but cannot connect to bluetooth headphones Sennheiser
  Momentum 3

Status in bluez package in Ubuntu:
  New

Bug description:

  I think that the issue might be partly because I have pulseaudio-bt-
  modules package with alternative codecs

  I removed tht package but still same issue

  lut 07 22:14:40 graf bluetoothd[1366]: Bluetooth daemon 5.53
  lut 07 22:14:40 graf systemd[1]: Started Bluetooth service.
  lut 07 22:14:40 graf bluetoothd[1366]: Starting SDP server
  lut 07 22:14:40 graf bluetoothd[1366]: Bluetooth management interface 1.20 
initialized
  lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSource/VENDOR/LDAC
  lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSource/VENDOR/APTXHD
  lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSource/VENDOR/APTX
  lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSource/AAC
  lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSource/SBC
  lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSink/VENDOR/APTXHD
  lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSink/VENDOR/APTX
  lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSink/AAC
  lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSink/SBC
  lut 08 08:37:50 graf bluetoothd[1366]: Terminating
  ...skipping...
  maj 10 13:20:34 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:21:44 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:22:53 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:24:02 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:25:12 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:26:21 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:27:31 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:28:40 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:29:50 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:31:00 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:32:09 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:33:18 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:34:27 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:35:36 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:36:46 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:37:55 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:39:05 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:40:14 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:41:24 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:42:34 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:43:43 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:44:53 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:46:02 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:47:11 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:48:21 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:49:30 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:50:40 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:51:49 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:52:59 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:54:08 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:55:18 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:56:27 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:57:36 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:58:45 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:59:55 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 14:01:05 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 14:02:14 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 14:03:23 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 14:04:33 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 14:05:42 

[Kernel-packages] [Bug 1972831] Re: Can pair but cannot connect to bluetooth headphones Sennheiser Momentum 3

2022-05-10 Thread mastier1
Seems there's no default dependency neither on ubuntu-desktop or
bluetooth meta package

-- 
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/1972831

Title:
  Can pair but cannot connect to bluetooth headphones Sennheiser
  Momentum 3

Status in bluez package in Ubuntu:
  New

Bug description:

  I think that the issue might be partly because I have pulseaudio-bt-
  modules package with alternative codecs

  I removed tht package but still same issue

  lut 07 22:14:40 graf bluetoothd[1366]: Bluetooth daemon 5.53
  lut 07 22:14:40 graf systemd[1]: Started Bluetooth service.
  lut 07 22:14:40 graf bluetoothd[1366]: Starting SDP server
  lut 07 22:14:40 graf bluetoothd[1366]: Bluetooth management interface 1.20 
initialized
  lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSource/VENDOR/LDAC
  lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSource/VENDOR/APTXHD
  lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSource/VENDOR/APTX
  lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSource/AAC
  lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSource/SBC
  lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSink/VENDOR/APTXHD
  lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSink/VENDOR/APTX
  lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSink/AAC
  lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSink/SBC
  lut 08 08:37:50 graf bluetoothd[1366]: Terminating
  ...skipping...
  maj 10 13:20:34 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:21:44 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:22:53 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:24:02 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:25:12 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:26:21 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:27:31 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:28:40 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:29:50 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:31:00 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:32:09 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:33:18 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:34:27 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:35:36 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:36:46 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:37:55 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:39:05 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:40:14 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:41:24 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:42:34 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:43:43 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:44:53 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:46:02 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:47:11 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:48:21 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:49:30 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:50:40 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:51:49 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:52:59 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:54:08 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:55:18 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:56:27 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:57:36 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:58:45 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:59:55 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 14:01:05 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 14:02:14 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 14:03:23 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 14:04:33 graf bluetoothd[1293]: Controller 

[Kernel-packages] [Bug 1972831] Re: Can pair but cannot connect to bluetooth headphones Sennheiser Momentum 3

2022-05-10 Thread mastier1
Ok,seems the culprit was missing package, not installed

$ sudo apt install pulseaudio-module-bluetooth
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  pulseaudio-module-bluetooth
0 upgraded, 1 newly installed, 0 to remove and 16 not upgraded.
Need to get 99,0 kB of archives.
After this operation, 430 kB of additional disk space will be used.
Get:1 http://pl.archive.ubuntu.com/ubuntu jammy/main amd64 
pulseaudio-module-bluetooth amd64 1:15.99.1+dfsg1-1ubuntu1 [99,0 kB]
Fetched 99,0 kB in 0s (758 kB/s)   
Selecting previously unselected package pulseaudio-module-bluetooth.
(Reading database ... 310011 files and directories currently installed.)
Preparing to unpack 
.../pulseaudio-module-bluetooth_1%3a15.99.1+dfsg1-1ubuntu1_amd64.deb ...
Unpacking pulseaudio-module-bluetooth (1:15.99.1+dfsg1-1ubuntu1) ...
Setting up pulseaudio-module-bluetooth (1:15.99.1+dfsg1-1ubuntu1) ...

-- 
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/1972831

Title:
  Can pair but cannot connect to bluetooth headphones Sennheiser
  Momentum 3

Status in bluez package in Ubuntu:
  New

Bug description:

  I think that the issue might be partly because I have pulseaudio-bt-
  modules package with alternative codecs

  I removed tht package but still same issue

  lut 07 22:14:40 graf bluetoothd[1366]: Bluetooth daemon 5.53
  lut 07 22:14:40 graf systemd[1]: Started Bluetooth service.
  lut 07 22:14:40 graf bluetoothd[1366]: Starting SDP server
  lut 07 22:14:40 graf bluetoothd[1366]: Bluetooth management interface 1.20 
initialized
  lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSource/VENDOR/LDAC
  lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSource/VENDOR/APTXHD
  lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSource/VENDOR/APTX
  lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSource/AAC
  lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSource/SBC
  lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSink/VENDOR/APTXHD
  lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSink/VENDOR/APTX
  lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSink/AAC
  lut 07 22:14:48 graf bluetoothd[1366]: Endpoint registered: sender=:1.82 
path=/MediaEndpoint/A2DPSink/SBC
  lut 08 08:37:50 graf bluetoothd[1366]: Terminating
  ...skipping...
  maj 10 13:20:34 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:21:44 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:22:53 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:24:02 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:25:12 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:26:21 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:27:31 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:28:40 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:29:50 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:31:00 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:32:09 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:33:18 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:34:27 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:35:36 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:36:46 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:37:55 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:39:05 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:40:14 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:41:24 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:42:34 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:43:43 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:44:53 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:46:02 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:47:11 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:48:21 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:49:30 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10 13:50:40 graf bluetoothd[1293]: Controller resume with wake event 0x0
  maj 10