[Touch-packages] [Bug 1962807] Re: segfault in libgtk-x11-2.0.so.0 with several programs

2022-03-02 Thread Sebastien Bacher
Thank you for your bug report. Was that a one time issue that trigger at
a specific time or at those software broken for you now?

** Summary changed:

- segfault in libgt-x11-2.0.so.0 with several programs
+ segfault in libgtk-x11-2.0.so.0 with several programs

** Changed in: gtk+2.0 (Ubuntu)
   Importance: Undecided => Low

** Changed in: gtk+2.0 (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1962807

Title:
  segfault in libgtk-x11-2.0.so.0 with several programs

Status in gtk+2.0 package in Ubuntu:
  Incomplete

Bug description:
  Today I have been encountering segfaults in fcl and virtualbox:

  Mar  2 07:20:40 Z560 kernel: [817210.808918] show_signal_msg: 12 callbacks 
suppressed
  Mar  2 07:20:40 Z560 kernel: [817210.808922] fcl[933482]: segfault at 
7fb98814fdb8 ip 7fb96efab218 sp 7ffc4a89b918 error 4 in 
libgtk-x11-2.0.so.0.2400.32[7fb96ed5b000+27]
  Mar  2 07:20:40 Z560 kernel: [817210.808932] Code: 79 db ff 48 83 c4 20 5b 5d 
41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 
0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 
c0 74 12
  Mar  2 07:20:40 Z560 systemd[1]: Created slice 
system-systemd\x2dcoredump.slice.
  Mar  2 07:20:40 Z560 systemd[1]: Started Process Core Dump (PID 933484/UID 0).
  Mar  2 07:20:40 Z560 systemd-coredump[933485]: Process 933482 (fcl) of user 
1000 dumped core.#012#012Stack trace of thread 933482:#012#0  
0x7fb96efab218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 
0x2b4218)#012#1  0x0002 n/a (n/a + 0x0)
  Mar  2 07:20:40 Z560 systemd[1]: systemd-coredump@0-933484-0.service: 
Succeeded.

  and:

  Mar  2 07:51:19 Z560 kernel: [819049.877381] VirtualBox[936782]: segfault at 
7ff8860b4db8 ip 7ff86cf10218 sp 7ffdd1a53758 error 4 in 
libgtk-x11-2.0.so.0.2400.32[7ff86ccc+27]
  Mar  2 07:51:19 Z560 kernel: [819049.877395] Code: 79 db ff 48 83 c4 20 5b 5d 
41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 
0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 
c0 74 12
  Mar  2 07:51:19 Z560 systemd[1]: Started Process Core Dump (PID 936794/UID 0).
  Mar  2 07:51:19 Z560 systemd-coredump[936795]: Process 936782 (VirtualBox) of 
user 1000 dumped core.#012#012Stack trace of thread 936782:#012#0  
0x7ff86cf10218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 
0x2b4218)#012#1  0x0002 n/a (n/a + 0x0)
  Mar  2 07:51:19 Z560 systemd[1]: systemd-coredump@10-936794-0.service: 
Succeeded.

  
  As this library has not changed I am assuming the problem is with one of the 
libraries it depends upon.  Several packages were updated in the past few days, 
I believe including some that may be the cause of the problem.  I have attached 
a zip with my /var/log/apt/term.log and history.log for inspection.

  Version of library is 2.24.32-4ubuntu4 and library file is dated
  2021-03-31 here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1962807/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1961859] Re: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI.

2022-03-02 Thread DengYi(Fibocom)
-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1961859

Title:
  When we install ModemManager1.16.6 and others, this will lead to
  ubuntu can not enter into GNOME UI.

Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  1. We use sourcecode to install ModemManger1.16.6
  2. Ubuntu can not enter UI.
  3. We capture log and picture and add these on the attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1961859/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1961859] Re: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI.

2022-03-02 Thread DengYi(Fibocom)
Hi:
   Our test step:
1. We install the Fibocom msdk(driver and MM1.16.6)
2. Install lenovo DPR service
3. if other software(eg:minicom) is installed, the crash problem is almost 
inevitable.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1961859

Title:
  When we install ModemManager1.16.6 and others, this will lead to
  ubuntu can not enter into GNOME UI.

Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  1. We use sourcecode to install ModemManger1.16.6
  2. Ubuntu can not enter UI.
  3. We capture log and picture and add these on the attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1961859/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1962818] [NEW] Jammy Jellyfish LightDM is frozen after long period of inactivity

2022-03-02 Thread Alex Powell
Public bug reported:

Jammy Jellyfish LightDM is frozen after long period of inactivity
Latest updates installed, has been happening since first install 2 weeks ago. 

Upon using the laptop after over night or coming back from work, the
screen is frozen. I can move the mouse around but click is unresponsive.

To resolve the issue, I ctrl=alt=f2 in order to log into a shell then
restart the LightDM services. Those equals signs should be a plus,
however it appears my shift key is not working so I will log another bug
for that.

I am using an XFCE environment.

Description:Ubuntu Jammy Jellyfish (development branch)
Release:22.04

lightdm:
  Installed: 1.30.0-0ubuntu5
  Candidate: 1.30.0-0ubuntu5
  Version table:
 *** 1.30.0-0ubuntu5 500
500 http://au.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
100 /var/lib/dpkg/status

** Affects: lightdm (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: ubiquity (Ubuntu) => lightdm (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1962818

Title:
  Jammy Jellyfish LightDM is frozen after long period of inactivity

Status in lightdm package in Ubuntu:
  New

Bug description:
  Jammy Jellyfish LightDM is frozen after long period of inactivity
  Latest updates installed, has been happening since first install 2 weeks ago. 

  Upon using the laptop after over night or coming back from work, the
  screen is frozen. I can move the mouse around but click is
  unresponsive.

  To resolve the issue, I ctrl=alt=f2 in order to log into a shell then
  restart the LightDM services. Those equals signs should be a plus,
  however it appears my shift key is not working so I will log another
  bug for that.

  I am using an XFCE environment.

  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04

  lightdm:
Installed: 1.30.0-0ubuntu5
Candidate: 1.30.0-0ubuntu5
Version table:
   *** 1.30.0-0ubuntu5 500
  500 http://au.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1962818/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1962818] [NEW] Jammy Jellyfish LightDM is frozen after long period of inactivity

2022-03-02 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Jammy Jellyfish LightDM is frozen after long period of inactivity
Latest updates installed, has been happening since first install 2 weeks ago. 

Upon using the laptop after over night or coming back from work, the
screen is frozen. I can move the mouse around but click is unresponsive.

To resolve the issue, I ctrl=alt=f2 in order to log into a shell then
restart the LightDM services. Those equals signs should be a plus,
however it appears my shift key is not working so I will log another bug
for that.

I am using an XFCE environment.

Description:Ubuntu Jammy Jellyfish (development branch)
Release:22.04

lightdm:
  Installed: 1.30.0-0ubuntu5
  Candidate: 1.30.0-0ubuntu5
  Version table:
 *** 1.30.0-0ubuntu5 500
500 http://au.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
100 /var/lib/dpkg/status

** Affects: lightdm (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Jammy Jellyfish LightDM is frozen after long period of inactivity
https://bugs.launchpad.net/bugs/1962818
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to lightdm in Ubuntu.

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1962769] Re: Could not receive advertising events: Broken pipe

2022-03-02 Thread Daniel van Vugt
Thanks for the bug report.

It appears you have modified Bluetooth binaries that are not from Ubuntu
so we can't support them here. The only supported version of bluez on
Ubuntu 20.04 is 5.53-0ubuntu3.5.

Although I do note that you are using:

  Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

and that Cambridge Silicon Radio dongles are notoriously buggy. So I
would first recommend trying a different brand of Bluetooth dongle.
Unfortunately it is hard to know what chipset is inside before you buy
it.

If you would like to continue with bug reports then please start by
installing the Ubuntu-provided bluez packages and then open a new bug.



** Changed in: bluez (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769

Title:
  Could not receive advertising events: Broken pipe

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  If a host has 2 adapters, the scanner run for a few second then get an
  error msg Could not receive advertising events: Broken pipe, then hci0
  turns down when I run hciconfig

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  DOWN
  RX bytes:574 acl:0 sco:0 events:30 errors:0
  TX bytes:368 acl:0 sco:0 commands:30 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221883 acl:0 sco:0 events:8327 errors:0
  TX bytes:1027 acl:0 sco:0 commands:67 errors:0

  
  This happend after I updated bluez from 5.62 to 5.63.

  If I do scan again, everything works fine with one adapter.

  
  As both adapters use the same mac address, I changed the address of hci0

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:01:07:00:47:0E  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:1184 acl:0 sco:0 events:66 errors:0
  TX bytes:1072 acl:0 sco:0 commands:66 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221961 acl:0 sco:0 events:8340 errors:0
  TX bytes:3078 acl:0 sco:0 commands:80 errors:0

  
  but the old address keeps reverted back which was not the case in 5.62

  I ran scan again while running btmon

  @ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0] 
1052.238244
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address al..   
1052.238720
  = bluetoothd: Failed to create GATT database for adapter [hci0] 
1052.238742
  = bluetoothd: Unable to register new adapter [hci0] 
1052.238761
  = Close Index: 00:1A:7D:DA:71:13 [hci0] 
1054.246981

  @ MGMT Event: Index Added (0x0004) plen 0 

 {0x0001} [hci0] 98.950611
  @ MGMT Command: Read Controller Information (0x0004) plen 0   

 {0x0001} [hci0] 98.950707
  @ MGMT Event: Command Complete (0x0001) plen 283  

 {0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration

[Touch-packages] [Bug 1962769] Re: Could not receive advertising events: Broken pipe

2022-03-02 Thread Daniel van Vugt
If you would like support for a version of BlueZ that you built yourself
then please go to https://github.com/bluez/bluez/issues/

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769

Title:
  Could not receive advertising events: Broken pipe

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  If a host has 2 adapters, the scanner run for a few second then get an
  error msg Could not receive advertising events: Broken pipe, then hci0
  turns down when I run hciconfig

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  DOWN
  RX bytes:574 acl:0 sco:0 events:30 errors:0
  TX bytes:368 acl:0 sco:0 commands:30 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221883 acl:0 sco:0 events:8327 errors:0
  TX bytes:1027 acl:0 sco:0 commands:67 errors:0

  
  This happend after I updated bluez from 5.62 to 5.63.

  If I do scan again, everything works fine with one adapter.

  
  As both adapters use the same mac address, I changed the address of hci0

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:01:07:00:47:0E  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:1184 acl:0 sco:0 events:66 errors:0
  TX bytes:1072 acl:0 sco:0 commands:66 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221961 acl:0 sco:0 events:8340 errors:0
  TX bytes:3078 acl:0 sco:0 commands:80 errors:0

  
  but the old address keeps reverted back which was not the case in 5.62

  I ran scan again while running btmon

  @ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0] 
1052.238244
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address al..   
1052.238720
  = bluetoothd: Failed to create GATT database for adapter [hci0] 
1052.238742
  = bluetoothd: Unable to register new adapter [hci0] 
1052.238761
  = Close Index: 00:1A:7D:DA:71:13 [hci0] 
1054.246981

  @ MGMT Event: Index Added (0x0004) plen 0 

 {0x0001} [hci0] 98.950611
  @ MGMT Command: Read Controller Information (0x0004) plen 0   

 {0x0001} [hci0] 98.950707
  @ MGMT Event: Command Complete (0x0001) plen 283  

 {0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address already in use 
(98)
   98.951201
  = bluetoothd: Failed to create GATT database for adapter  

  [hci0] 98.951229
  = 

[Touch-packages] [Bug 1962807] [NEW] segfault in libgt-x11-2.0.so.0 with several programs

2022-03-02 Thread dhdur...@verizon.net
Public bug reported:

Today I have been encountering segfaults in fcl and virtualbox:

Mar  2 07:20:40 Z560 kernel: [817210.808918] show_signal_msg: 12 callbacks 
suppressed
Mar  2 07:20:40 Z560 kernel: [817210.808922] fcl[933482]: segfault at 
7fb98814fdb8 ip 7fb96efab218 sp 7ffc4a89b918 error 4 in 
libgtk-x11-2.0.so.0.2400.32[7fb96ed5b000+27]
Mar  2 07:20:40 Z560 kernel: [817210.808932] Code: 79 db ff 48 83 c4 20 5b 5d 
41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 
0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 
c0 74 12
Mar  2 07:20:40 Z560 systemd[1]: Created slice system-systemd\x2dcoredump.slice.
Mar  2 07:20:40 Z560 systemd[1]: Started Process Core Dump (PID 933484/UID 0).
Mar  2 07:20:40 Z560 systemd-coredump[933485]: Process 933482 (fcl) of user 
1000 dumped core.#012#012Stack trace of thread 933482:#012#0  
0x7fb96efab218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 
0x2b4218)#012#1  0x0002 n/a (n/a + 0x0)
Mar  2 07:20:40 Z560 systemd[1]: systemd-coredump@0-933484-0.service: Succeeded.

and:

Mar  2 07:51:19 Z560 kernel: [819049.877381] VirtualBox[936782]: segfault at 
7ff8860b4db8 ip 7ff86cf10218 sp 7ffdd1a53758 error 4 in 
libgtk-x11-2.0.so.0.2400.32[7ff86ccc+27]
Mar  2 07:51:19 Z560 kernel: [819049.877395] Code: 79 db ff 48 83 c4 20 5b 5d 
41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 
0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 
c0 74 12
Mar  2 07:51:19 Z560 systemd[1]: Started Process Core Dump (PID 936794/UID 0).
Mar  2 07:51:19 Z560 systemd-coredump[936795]: Process 936782 (VirtualBox) of 
user 1000 dumped core.#012#012Stack trace of thread 936782:#012#0  
0x7ff86cf10218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 
0x2b4218)#012#1  0x0002 n/a (n/a + 0x0)
Mar  2 07:51:19 Z560 systemd[1]: systemd-coredump@10-936794-0.service: 
Succeeded.


As this library has not changed I am assuming the problem is with one of the 
libraries it depends upon.  Several packages were updated in the past few days, 
I believe including some that may be the cause of the problem.  I have attached 
a zip with my /var/log/apt/term.log and history.log for inspection.

Version of library is 2.24.32-4ubuntu4 and library file is dated
2021-03-31 here.

** Affects: gtk+2.0 (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "apt-log.zip"
   
https://bugs.launchpad.net/bugs/1962807/+attachment/5565153/+files/apt-log.zip

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1962807

Title:
  segfault in libgt-x11-2.0.so.0 with several programs

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  Today I have been encountering segfaults in fcl and virtualbox:

  Mar  2 07:20:40 Z560 kernel: [817210.808918] show_signal_msg: 12 callbacks 
suppressed
  Mar  2 07:20:40 Z560 kernel: [817210.808922] fcl[933482]: segfault at 
7fb98814fdb8 ip 7fb96efab218 sp 7ffc4a89b918 error 4 in 
libgtk-x11-2.0.so.0.2400.32[7fb96ed5b000+27]
  Mar  2 07:20:40 Z560 kernel: [817210.808932] Code: 79 db ff 48 83 c4 20 5b 5d 
41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 
0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 
c0 74 12
  Mar  2 07:20:40 Z560 systemd[1]: Created slice 
system-systemd\x2dcoredump.slice.
  Mar  2 07:20:40 Z560 systemd[1]: Started Process Core Dump (PID 933484/UID 0).
  Mar  2 07:20:40 Z560 systemd-coredump[933485]: Process 933482 (fcl) of user 
1000 dumped core.#012#012Stack trace of thread 933482:#012#0  
0x7fb96efab218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 
0x2b4218)#012#1  0x0002 n/a (n/a + 0x0)
  Mar  2 07:20:40 Z560 systemd[1]: systemd-coredump@0-933484-0.service: 
Succeeded.

  and:

  Mar  2 07:51:19 Z560 kernel: [819049.877381] VirtualBox[936782]: segfault at 
7ff8860b4db8 ip 7ff86cf10218 sp 7ffdd1a53758 error 4 in 
libgtk-x11-2.0.so.0.2400.32[7ff86ccc+27]
  Mar  2 07:51:19 Z560 kernel: [819049.877395] Code: 79 db ff 48 83 c4 20 5b 5d 
41 5c c3 66 0f 1f 44 00 00 48 8b b7 90 00 00 79 48 89 d7 e9 c1 a1 db 58 90 f3 
0f 1e fa 48 83 d9 18 <48> 8b 05 99 4b 1a 19 48 89 44 24 08 48 8b 5d 24 08 48 85 
c0 74 12
  Mar  2 07:51:19 Z560 systemd[1]: Started Process Core Dump (PID 936794/UID 0).
  Mar  2 07:51:19 Z560 systemd-coredump[936795]: Process 936782 (VirtualBox) of 
user 1000 dumped core.#012#012Stack trace of thread 936782:#012#0  
0x7ff86cf10218 gtk_option_menu_get_type (libgtk-x11-2.0.so.0 + 
0x2b4218)#012#1  0x0002 n/a (n/a + 0x0)
  Mar  2 07:51:19 Z560 systemd[1]: systemd-coredump@10-936794-0.service: 
Succeeded.

  
  As this library has not changed I am assuming the problem is with one of the 
libraries it depends upon.  Several 

[Touch-packages] [Bug 1962769] rfkill.txt

2022-03-02 Thread Rabee
apport information

** Attachment added: "rfkill.txt"
   https://bugs.launchpad.net/bugs/1962769/+attachment/5565133/+files/rfkill.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769

Title:
  Could not receive advertising events: Broken pipe

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  If a host has 2 adapters, the scanner run for a few second then get an
  error msg Could not receive advertising events: Broken pipe, then hci0
  turns down when I run hciconfig

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  DOWN
  RX bytes:574 acl:0 sco:0 events:30 errors:0
  TX bytes:368 acl:0 sco:0 commands:30 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221883 acl:0 sco:0 events:8327 errors:0
  TX bytes:1027 acl:0 sco:0 commands:67 errors:0

  
  This happend after I updated bluez from 5.62 to 5.63.

  If I do scan again, everything works fine with one adapter.

  
  As both adapters use the same mac address, I changed the address of hci0

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:01:07:00:47:0E  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:1184 acl:0 sco:0 events:66 errors:0
  TX bytes:1072 acl:0 sco:0 commands:66 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221961 acl:0 sco:0 events:8340 errors:0
  TX bytes:3078 acl:0 sco:0 commands:80 errors:0

  
  but the old address keeps reverted back which was not the case in 5.62

  I ran scan again while running btmon

  @ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0] 
1052.238244
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address al..   
1052.238720
  = bluetoothd: Failed to create GATT database for adapter [hci0] 
1052.238742
  = bluetoothd: Unable to register new adapter [hci0] 
1052.238761
  = Close Index: 00:1A:7D:DA:71:13 [hci0] 
1054.246981

  @ MGMT Event: Index Added (0x0004) plen 0 

 {0x0001} [hci0] 98.950611
  @ MGMT Command: Read Controller Information (0x0004) plen 0   

 {0x0001} [hci0] 98.950707
  @ MGMT Event: Command Complete (0x0001) plen 283  

 {0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address already in use 
(98)
   98.951201
  = bluetoothd: Failed to create GATT database for adapter  

  [hci0] 98.951229
  = 

[Touch-packages] [Bug 1962769] getfacl.txt

2022-03-02 Thread Rabee
apport information

** Attachment added: "getfacl.txt"
   
https://bugs.launchpad.net/bugs/1962769/+attachment/5565129/+files/getfacl.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769

Title:
  Could not receive advertising events: Broken pipe

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  If a host has 2 adapters, the scanner run for a few second then get an
  error msg Could not receive advertising events: Broken pipe, then hci0
  turns down when I run hciconfig

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  DOWN
  RX bytes:574 acl:0 sco:0 events:30 errors:0
  TX bytes:368 acl:0 sco:0 commands:30 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221883 acl:0 sco:0 events:8327 errors:0
  TX bytes:1027 acl:0 sco:0 commands:67 errors:0

  
  This happend after I updated bluez from 5.62 to 5.63.

  If I do scan again, everything works fine with one adapter.

  
  As both adapters use the same mac address, I changed the address of hci0

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:01:07:00:47:0E  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:1184 acl:0 sco:0 events:66 errors:0
  TX bytes:1072 acl:0 sco:0 commands:66 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221961 acl:0 sco:0 events:8340 errors:0
  TX bytes:3078 acl:0 sco:0 commands:80 errors:0

  
  but the old address keeps reverted back which was not the case in 5.62

  I ran scan again while running btmon

  @ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0] 
1052.238244
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address al..   
1052.238720
  = bluetoothd: Failed to create GATT database for adapter [hci0] 
1052.238742
  = bluetoothd: Unable to register new adapter [hci0] 
1052.238761
  = Close Index: 00:1A:7D:DA:71:13 [hci0] 
1054.246981

  @ MGMT Event: Index Added (0x0004) plen 0 

 {0x0001} [hci0] 98.950611
  @ MGMT Command: Read Controller Information (0x0004) plen 0   

 {0x0001} [hci0] 98.950707
  @ MGMT Event: Command Complete (0x0001) plen 283  

 {0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address already in use 
(98)
   98.951201
  = bluetoothd: Failed to create GATT database for adapter  

  [hci0] 98.951229
 

[Touch-packages] [Bug 1962769] Lsusb-v.txt

2022-03-02 Thread Rabee
apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1962769/+attachment/5565123/+files/Lsusb-v.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769

Title:
  Could not receive advertising events: Broken pipe

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  If a host has 2 adapters, the scanner run for a few second then get an
  error msg Could not receive advertising events: Broken pipe, then hci0
  turns down when I run hciconfig

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  DOWN
  RX bytes:574 acl:0 sco:0 events:30 errors:0
  TX bytes:368 acl:0 sco:0 commands:30 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221883 acl:0 sco:0 events:8327 errors:0
  TX bytes:1027 acl:0 sco:0 commands:67 errors:0

  
  This happend after I updated bluez from 5.62 to 5.63.

  If I do scan again, everything works fine with one adapter.

  
  As both adapters use the same mac address, I changed the address of hci0

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:01:07:00:47:0E  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:1184 acl:0 sco:0 events:66 errors:0
  TX bytes:1072 acl:0 sco:0 commands:66 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221961 acl:0 sco:0 events:8340 errors:0
  TX bytes:3078 acl:0 sco:0 commands:80 errors:0

  
  but the old address keeps reverted back which was not the case in 5.62

  I ran scan again while running btmon

  @ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0] 
1052.238244
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address al..   
1052.238720
  = bluetoothd: Failed to create GATT database for adapter [hci0] 
1052.238742
  = bluetoothd: Unable to register new adapter [hci0] 
1052.238761
  = Close Index: 00:1A:7D:DA:71:13 [hci0] 
1054.246981

  @ MGMT Event: Index Added (0x0004) plen 0 

 {0x0001} [hci0] 98.950611
  @ MGMT Command: Read Controller Information (0x0004) plen 0   

 {0x0001} [hci0] 98.950707
  @ MGMT Event: Command Complete (0x0001) plen 283  

 {0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address already in use 
(98)
   98.951201
  = bluetoothd: Failed to create GATT database for adapter  

  [hci0] 98.951229
 

[Touch-packages] [Bug 1962769] modified.conffile..etc.dbus-1.system.d.bluetooth.conf.txt

2022-03-02 Thread Rabee
apport information

** Attachment added: "modified.conffile..etc.dbus-1.system.d.bluetooth.conf.txt"
   
https://bugs.launchpad.net/bugs/1962769/+attachment/5565132/+files/modified.conffile..etc.dbus-1.system.d.bluetooth.conf.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769

Title:
  Could not receive advertising events: Broken pipe

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  If a host has 2 adapters, the scanner run for a few second then get an
  error msg Could not receive advertising events: Broken pipe, then hci0
  turns down when I run hciconfig

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  DOWN
  RX bytes:574 acl:0 sco:0 events:30 errors:0
  TX bytes:368 acl:0 sco:0 commands:30 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221883 acl:0 sco:0 events:8327 errors:0
  TX bytes:1027 acl:0 sco:0 commands:67 errors:0

  
  This happend after I updated bluez from 5.62 to 5.63.

  If I do scan again, everything works fine with one adapter.

  
  As both adapters use the same mac address, I changed the address of hci0

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:01:07:00:47:0E  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:1184 acl:0 sco:0 events:66 errors:0
  TX bytes:1072 acl:0 sco:0 commands:66 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221961 acl:0 sco:0 events:8340 errors:0
  TX bytes:3078 acl:0 sco:0 commands:80 errors:0

  
  but the old address keeps reverted back which was not the case in 5.62

  I ran scan again while running btmon

  @ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0] 
1052.238244
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address al..   
1052.238720
  = bluetoothd: Failed to create GATT database for adapter [hci0] 
1052.238742
  = bluetoothd: Unable to register new adapter [hci0] 
1052.238761
  = Close Index: 00:1A:7D:DA:71:13 [hci0] 
1054.246981

  @ MGMT Event: Index Added (0x0004) plen 0 

 {0x0001} [hci0] 98.950611
  @ MGMT Command: Read Controller Information (0x0004) plen 0   

 {0x0001} [hci0] 98.950707
  @ MGMT Event: Command Complete (0x0001) plen 283  

 {0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address already in use 
(98)
   98.951201
  = bluetoothd: Failed to create GATT database for adapter  
 

[Touch-packages] [Bug 1962769] hciconfig.txt

2022-03-02 Thread Rabee
apport information

** Attachment added: "hciconfig.txt"
   
https://bugs.launchpad.net/bugs/1962769/+attachment/5565130/+files/hciconfig.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769

Title:
  Could not receive advertising events: Broken pipe

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  If a host has 2 adapters, the scanner run for a few second then get an
  error msg Could not receive advertising events: Broken pipe, then hci0
  turns down when I run hciconfig

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  DOWN
  RX bytes:574 acl:0 sco:0 events:30 errors:0
  TX bytes:368 acl:0 sco:0 commands:30 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221883 acl:0 sco:0 events:8327 errors:0
  TX bytes:1027 acl:0 sco:0 commands:67 errors:0

  
  This happend after I updated bluez from 5.62 to 5.63.

  If I do scan again, everything works fine with one adapter.

  
  As both adapters use the same mac address, I changed the address of hci0

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:01:07:00:47:0E  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:1184 acl:0 sco:0 events:66 errors:0
  TX bytes:1072 acl:0 sco:0 commands:66 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221961 acl:0 sco:0 events:8340 errors:0
  TX bytes:3078 acl:0 sco:0 commands:80 errors:0

  
  but the old address keeps reverted back which was not the case in 5.62

  I ran scan again while running btmon

  @ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0] 
1052.238244
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address al..   
1052.238720
  = bluetoothd: Failed to create GATT database for adapter [hci0] 
1052.238742
  = bluetoothd: Unable to register new adapter [hci0] 
1052.238761
  = Close Index: 00:1A:7D:DA:71:13 [hci0] 
1054.246981

  @ MGMT Event: Index Added (0x0004) plen 0 

 {0x0001} [hci0] 98.950611
  @ MGMT Command: Read Controller Information (0x0004) plen 0   

 {0x0001} [hci0] 98.950707
  @ MGMT Event: Command Complete (0x0001) plen 283  

 {0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address already in use 
(98)
   98.951201
  = bluetoothd: Failed to create GATT database for adapter  

  [hci0] 

[Touch-packages] [Bug 1962769] modified.conffile..etc.bluetooth.main.conf.txt

2022-03-02 Thread Rabee
apport information

** Attachment added: "modified.conffile..etc.bluetooth.main.conf.txt"
   
https://bugs.launchpad.net/bugs/1962769/+attachment/5565131/+files/modified.conffile..etc.bluetooth.main.conf.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769

Title:
  Could not receive advertising events: Broken pipe

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  If a host has 2 adapters, the scanner run for a few second then get an
  error msg Could not receive advertising events: Broken pipe, then hci0
  turns down when I run hciconfig

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  DOWN
  RX bytes:574 acl:0 sco:0 events:30 errors:0
  TX bytes:368 acl:0 sco:0 commands:30 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221883 acl:0 sco:0 events:8327 errors:0
  TX bytes:1027 acl:0 sco:0 commands:67 errors:0

  
  This happend after I updated bluez from 5.62 to 5.63.

  If I do scan again, everything works fine with one adapter.

  
  As both adapters use the same mac address, I changed the address of hci0

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:01:07:00:47:0E  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:1184 acl:0 sco:0 events:66 errors:0
  TX bytes:1072 acl:0 sco:0 commands:66 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221961 acl:0 sco:0 events:8340 errors:0
  TX bytes:3078 acl:0 sco:0 commands:80 errors:0

  
  but the old address keeps reverted back which was not the case in 5.62

  I ran scan again while running btmon

  @ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0] 
1052.238244
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address al..   
1052.238720
  = bluetoothd: Failed to create GATT database for adapter [hci0] 
1052.238742
  = bluetoothd: Unable to register new adapter [hci0] 
1052.238761
  = Close Index: 00:1A:7D:DA:71:13 [hci0] 
1054.246981

  @ MGMT Event: Index Added (0x0004) plen 0 

 {0x0001} [hci0] 98.950611
  @ MGMT Command: Read Controller Information (0x0004) plen 0   

 {0x0001} [hci0] 98.950707
  @ MGMT Event: Command Complete (0x0001) plen 283  

 {0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address already in use 
(98)
   98.951201
  = bluetoothd: Failed to create GATT database for adapter  
   

[Touch-packages] [Bug 1962769] ProcCpuinfo.txt

2022-03-02 Thread Rabee
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1962769/+attachment/5565124/+files/ProcCpuinfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769

Title:
  Could not receive advertising events: Broken pipe

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  If a host has 2 adapters, the scanner run for a few second then get an
  error msg Could not receive advertising events: Broken pipe, then hci0
  turns down when I run hciconfig

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  DOWN
  RX bytes:574 acl:0 sco:0 events:30 errors:0
  TX bytes:368 acl:0 sco:0 commands:30 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221883 acl:0 sco:0 events:8327 errors:0
  TX bytes:1027 acl:0 sco:0 commands:67 errors:0

  
  This happend after I updated bluez from 5.62 to 5.63.

  If I do scan again, everything works fine with one adapter.

  
  As both adapters use the same mac address, I changed the address of hci0

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:01:07:00:47:0E  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:1184 acl:0 sco:0 events:66 errors:0
  TX bytes:1072 acl:0 sco:0 commands:66 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221961 acl:0 sco:0 events:8340 errors:0
  TX bytes:3078 acl:0 sco:0 commands:80 errors:0

  
  but the old address keeps reverted back which was not the case in 5.62

  I ran scan again while running btmon

  @ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0] 
1052.238244
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address al..   
1052.238720
  = bluetoothd: Failed to create GATT database for adapter [hci0] 
1052.238742
  = bluetoothd: Unable to register new adapter [hci0] 
1052.238761
  = Close Index: 00:1A:7D:DA:71:13 [hci0] 
1054.246981

  @ MGMT Event: Index Added (0x0004) plen 0 

 {0x0001} [hci0] 98.950611
  @ MGMT Command: Read Controller Information (0x0004) plen 0   

 {0x0001} [hci0] 98.950707
  @ MGMT Event: Command Complete (0x0001) plen 283  

 {0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address already in use 
(98)
   98.951201
  = bluetoothd: Failed to create GATT database for adapter  

  [hci0] 

[Touch-packages] [Bug 1962769] syslog.txt

2022-03-02 Thread Rabee
apport information

** Attachment added: "syslog.txt"
   https://bugs.launchpad.net/bugs/1962769/+attachment/5565134/+files/syslog.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769

Title:
  Could not receive advertising events: Broken pipe

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  If a host has 2 adapters, the scanner run for a few second then get an
  error msg Could not receive advertising events: Broken pipe, then hci0
  turns down when I run hciconfig

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  DOWN
  RX bytes:574 acl:0 sco:0 events:30 errors:0
  TX bytes:368 acl:0 sco:0 commands:30 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221883 acl:0 sco:0 events:8327 errors:0
  TX bytes:1027 acl:0 sco:0 commands:67 errors:0

  
  This happend after I updated bluez from 5.62 to 5.63.

  If I do scan again, everything works fine with one adapter.

  
  As both adapters use the same mac address, I changed the address of hci0

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:01:07:00:47:0E  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:1184 acl:0 sco:0 events:66 errors:0
  TX bytes:1072 acl:0 sco:0 commands:66 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221961 acl:0 sco:0 events:8340 errors:0
  TX bytes:3078 acl:0 sco:0 commands:80 errors:0

  
  but the old address keeps reverted back which was not the case in 5.62

  I ran scan again while running btmon

  @ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0] 
1052.238244
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address al..   
1052.238720
  = bluetoothd: Failed to create GATT database for adapter [hci0] 
1052.238742
  = bluetoothd: Unable to register new adapter [hci0] 
1052.238761
  = Close Index: 00:1A:7D:DA:71:13 [hci0] 
1054.246981

  @ MGMT Event: Index Added (0x0004) plen 0 

 {0x0001} [hci0] 98.950611
  @ MGMT Command: Read Controller Information (0x0004) plen 0   

 {0x0001} [hci0] 98.950707
  @ MGMT Event: Command Complete (0x0001) plen 283  

 {0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address already in use 
(98)
   98.951201
  = bluetoothd: Failed to create GATT database for adapter  

  [hci0] 98.951229
  = 

[Touch-packages] [Bug 1962769] UdevDb.txt

2022-03-02 Thread Rabee
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1962769/+attachment/5565128/+files/UdevDb.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769

Title:
  Could not receive advertising events: Broken pipe

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  If a host has 2 adapters, the scanner run for a few second then get an
  error msg Could not receive advertising events: Broken pipe, then hci0
  turns down when I run hciconfig

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  DOWN
  RX bytes:574 acl:0 sco:0 events:30 errors:0
  TX bytes:368 acl:0 sco:0 commands:30 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221883 acl:0 sco:0 events:8327 errors:0
  TX bytes:1027 acl:0 sco:0 commands:67 errors:0

  
  This happend after I updated bluez from 5.62 to 5.63.

  If I do scan again, everything works fine with one adapter.

  
  As both adapters use the same mac address, I changed the address of hci0

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:01:07:00:47:0E  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:1184 acl:0 sco:0 events:66 errors:0
  TX bytes:1072 acl:0 sco:0 commands:66 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221961 acl:0 sco:0 events:8340 errors:0
  TX bytes:3078 acl:0 sco:0 commands:80 errors:0

  
  but the old address keeps reverted back which was not the case in 5.62

  I ran scan again while running btmon

  @ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0] 
1052.238244
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address al..   
1052.238720
  = bluetoothd: Failed to create GATT database for adapter [hci0] 
1052.238742
  = bluetoothd: Unable to register new adapter [hci0] 
1052.238761
  = Close Index: 00:1A:7D:DA:71:13 [hci0] 
1054.246981

  @ MGMT Event: Index Added (0x0004) plen 0 

 {0x0001} [hci0] 98.950611
  @ MGMT Command: Read Controller Information (0x0004) plen 0   

 {0x0001} [hci0] 98.950707
  @ MGMT Event: Command Complete (0x0001) plen 283  

 {0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address already in use 
(98)
   98.951201
  = bluetoothd: Failed to create GATT database for adapter  

  [hci0] 98.951229
  = 

[Touch-packages] [Bug 1962769] ProcInterrupts.txt

2022-03-02 Thread Rabee
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1962769/+attachment/5565126/+files/ProcInterrupts.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769

Title:
  Could not receive advertising events: Broken pipe

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  If a host has 2 adapters, the scanner run for a few second then get an
  error msg Could not receive advertising events: Broken pipe, then hci0
  turns down when I run hciconfig

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  DOWN
  RX bytes:574 acl:0 sco:0 events:30 errors:0
  TX bytes:368 acl:0 sco:0 commands:30 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221883 acl:0 sco:0 events:8327 errors:0
  TX bytes:1027 acl:0 sco:0 commands:67 errors:0

  
  This happend after I updated bluez from 5.62 to 5.63.

  If I do scan again, everything works fine with one adapter.

  
  As both adapters use the same mac address, I changed the address of hci0

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:01:07:00:47:0E  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:1184 acl:0 sco:0 events:66 errors:0
  TX bytes:1072 acl:0 sco:0 commands:66 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221961 acl:0 sco:0 events:8340 errors:0
  TX bytes:3078 acl:0 sco:0 commands:80 errors:0

  
  but the old address keeps reverted back which was not the case in 5.62

  I ran scan again while running btmon

  @ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0] 
1052.238244
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address al..   
1052.238720
  = bluetoothd: Failed to create GATT database for adapter [hci0] 
1052.238742
  = bluetoothd: Unable to register new adapter [hci0] 
1052.238761
  = Close Index: 00:1A:7D:DA:71:13 [hci0] 
1054.246981

  @ MGMT Event: Index Added (0x0004) plen 0 

 {0x0001} [hci0] 98.950611
  @ MGMT Command: Read Controller Information (0x0004) plen 0   

 {0x0001} [hci0] 98.950707
  @ MGMT Event: Command Complete (0x0001) plen 283  

 {0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address already in use 
(98)
   98.951201
  = bluetoothd: Failed to create GATT database for adapter  

  

[Touch-packages] [Bug 1962769] ProcModules.txt

2022-03-02 Thread Rabee
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1962769/+attachment/5565127/+files/ProcModules.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769

Title:
  Could not receive advertising events: Broken pipe

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  If a host has 2 adapters, the scanner run for a few second then get an
  error msg Could not receive advertising events: Broken pipe, then hci0
  turns down when I run hciconfig

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  DOWN
  RX bytes:574 acl:0 sco:0 events:30 errors:0
  TX bytes:368 acl:0 sco:0 commands:30 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221883 acl:0 sco:0 events:8327 errors:0
  TX bytes:1027 acl:0 sco:0 commands:67 errors:0

  
  This happend after I updated bluez from 5.62 to 5.63.

  If I do scan again, everything works fine with one adapter.

  
  As both adapters use the same mac address, I changed the address of hci0

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:01:07:00:47:0E  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:1184 acl:0 sco:0 events:66 errors:0
  TX bytes:1072 acl:0 sco:0 commands:66 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221961 acl:0 sco:0 events:8340 errors:0
  TX bytes:3078 acl:0 sco:0 commands:80 errors:0

  
  but the old address keeps reverted back which was not the case in 5.62

  I ran scan again while running btmon

  @ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0] 
1052.238244
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address al..   
1052.238720
  = bluetoothd: Failed to create GATT database for adapter [hci0] 
1052.238742
  = bluetoothd: Unable to register new adapter [hci0] 
1052.238761
  = Close Index: 00:1A:7D:DA:71:13 [hci0] 
1054.246981

  @ MGMT Event: Index Added (0x0004) plen 0 

 {0x0001} [hci0] 98.950611
  @ MGMT Command: Read Controller Information (0x0004) plen 0   

 {0x0001} [hci0] 98.950707
  @ MGMT Event: Command Complete (0x0001) plen 283  

 {0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address already in use 
(98)
   98.951201
  = bluetoothd: Failed to create GATT database for adapter  

  [hci0] 

[Touch-packages] [Bug 1962769] ProcCpuinfoMinimal.txt

2022-03-02 Thread Rabee
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1962769/+attachment/5565125/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769

Title:
  Could not receive advertising events: Broken pipe

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  If a host has 2 adapters, the scanner run for a few second then get an
  error msg Could not receive advertising events: Broken pipe, then hci0
  turns down when I run hciconfig

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  DOWN
  RX bytes:574 acl:0 sco:0 events:30 errors:0
  TX bytes:368 acl:0 sco:0 commands:30 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221883 acl:0 sco:0 events:8327 errors:0
  TX bytes:1027 acl:0 sco:0 commands:67 errors:0

  
  This happend after I updated bluez from 5.62 to 5.63.

  If I do scan again, everything works fine with one adapter.

  
  As both adapters use the same mac address, I changed the address of hci0

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:01:07:00:47:0E  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:1184 acl:0 sco:0 events:66 errors:0
  TX bytes:1072 acl:0 sco:0 commands:66 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221961 acl:0 sco:0 events:8340 errors:0
  TX bytes:3078 acl:0 sco:0 commands:80 errors:0

  
  but the old address keeps reverted back which was not the case in 5.62

  I ran scan again while running btmon

  @ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0] 
1052.238244
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address al..   
1052.238720
  = bluetoothd: Failed to create GATT database for adapter [hci0] 
1052.238742
  = bluetoothd: Unable to register new adapter [hci0] 
1052.238761
  = Close Index: 00:1A:7D:DA:71:13 [hci0] 
1054.246981

  @ MGMT Event: Index Added (0x0004) plen 0 

 {0x0001} [hci0] 98.950611
  @ MGMT Command: Read Controller Information (0x0004) plen 0   

 {0x0001} [hci0] 98.950707
  @ MGMT Event: Command Complete (0x0001) plen 283  

 {0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address already in use 
(98)
   98.951201
  = bluetoothd: Failed to create GATT database for adapter  

  

[Touch-packages] [Bug 1962769] Lsusb-t.txt

2022-03-02 Thread Rabee
apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1962769/+attachment/5565122/+files/Lsusb-t.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769

Title:
  Could not receive advertising events: Broken pipe

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  If a host has 2 adapters, the scanner run for a few second then get an
  error msg Could not receive advertising events: Broken pipe, then hci0
  turns down when I run hciconfig

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  DOWN
  RX bytes:574 acl:0 sco:0 events:30 errors:0
  TX bytes:368 acl:0 sco:0 commands:30 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221883 acl:0 sco:0 events:8327 errors:0
  TX bytes:1027 acl:0 sco:0 commands:67 errors:0

  
  This happend after I updated bluez from 5.62 to 5.63.

  If I do scan again, everything works fine with one adapter.

  
  As both adapters use the same mac address, I changed the address of hci0

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:01:07:00:47:0E  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:1184 acl:0 sco:0 events:66 errors:0
  TX bytes:1072 acl:0 sco:0 commands:66 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221961 acl:0 sco:0 events:8340 errors:0
  TX bytes:3078 acl:0 sco:0 commands:80 errors:0

  
  but the old address keeps reverted back which was not the case in 5.62

  I ran scan again while running btmon

  @ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0] 
1052.238244
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address al..   
1052.238720
  = bluetoothd: Failed to create GATT database for adapter [hci0] 
1052.238742
  = bluetoothd: Unable to register new adapter [hci0] 
1052.238761
  = Close Index: 00:1A:7D:DA:71:13 [hci0] 
1054.246981

  @ MGMT Event: Index Added (0x0004) plen 0 

 {0x0001} [hci0] 98.950611
  @ MGMT Command: Read Controller Information (0x0004) plen 0   

 {0x0001} [hci0] 98.950707
  @ MGMT Event: Command Complete (0x0001) plen 283  

 {0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address already in use 
(98)
   98.951201
  = bluetoothd: Failed to create GATT database for adapter  

  [hci0] 98.951229
 

[Touch-packages] [Bug 1962769] Dependencies.txt

2022-03-02 Thread Rabee
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1962769/+attachment/5565118/+files/Dependencies.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769

Title:
  Could not receive advertising events: Broken pipe

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  If a host has 2 adapters, the scanner run for a few second then get an
  error msg Could not receive advertising events: Broken pipe, then hci0
  turns down when I run hciconfig

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  DOWN
  RX bytes:574 acl:0 sco:0 events:30 errors:0
  TX bytes:368 acl:0 sco:0 commands:30 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221883 acl:0 sco:0 events:8327 errors:0
  TX bytes:1027 acl:0 sco:0 commands:67 errors:0

  
  This happend after I updated bluez from 5.62 to 5.63.

  If I do scan again, everything works fine with one adapter.

  
  As both adapters use the same mac address, I changed the address of hci0

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:01:07:00:47:0E  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:1184 acl:0 sco:0 events:66 errors:0
  TX bytes:1072 acl:0 sco:0 commands:66 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221961 acl:0 sco:0 events:8340 errors:0
  TX bytes:3078 acl:0 sco:0 commands:80 errors:0

  
  but the old address keeps reverted back which was not the case in 5.62

  I ran scan again while running btmon

  @ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0] 
1052.238244
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address al..   
1052.238720
  = bluetoothd: Failed to create GATT database for adapter [hci0] 
1052.238742
  = bluetoothd: Unable to register new adapter [hci0] 
1052.238761
  = Close Index: 00:1A:7D:DA:71:13 [hci0] 
1054.246981

  @ MGMT Event: Index Added (0x0004) plen 0 

 {0x0001} [hci0] 98.950611
  @ MGMT Command: Read Controller Information (0x0004) plen 0   

 {0x0001} [hci0] 98.950707
  @ MGMT Event: Command Complete (0x0001) plen 283  

 {0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address already in use 
(98)
   98.951201
  = bluetoothd: Failed to create GATT database for adapter  

  [hci0] 

[Touch-packages] [Bug 1962769] Lspci-vt.txt

2022-03-02 Thread Rabee
apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1962769/+attachment/5565120/+files/Lspci-vt.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769

Title:
  Could not receive advertising events: Broken pipe

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  If a host has 2 adapters, the scanner run for a few second then get an
  error msg Could not receive advertising events: Broken pipe, then hci0
  turns down when I run hciconfig

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  DOWN
  RX bytes:574 acl:0 sco:0 events:30 errors:0
  TX bytes:368 acl:0 sco:0 commands:30 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221883 acl:0 sco:0 events:8327 errors:0
  TX bytes:1027 acl:0 sco:0 commands:67 errors:0

  
  This happend after I updated bluez from 5.62 to 5.63.

  If I do scan again, everything works fine with one adapter.

  
  As both adapters use the same mac address, I changed the address of hci0

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:01:07:00:47:0E  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:1184 acl:0 sco:0 events:66 errors:0
  TX bytes:1072 acl:0 sco:0 commands:66 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221961 acl:0 sco:0 events:8340 errors:0
  TX bytes:3078 acl:0 sco:0 commands:80 errors:0

  
  but the old address keeps reverted back which was not the case in 5.62

  I ran scan again while running btmon

  @ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0] 
1052.238244
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address al..   
1052.238720
  = bluetoothd: Failed to create GATT database for adapter [hci0] 
1052.238742
  = bluetoothd: Unable to register new adapter [hci0] 
1052.238761
  = Close Index: 00:1A:7D:DA:71:13 [hci0] 
1054.246981

  @ MGMT Event: Index Added (0x0004) plen 0 

 {0x0001} [hci0] 98.950611
  @ MGMT Command: Read Controller Information (0x0004) plen 0   

 {0x0001} [hci0] 98.950707
  @ MGMT Event: Command Complete (0x0001) plen 283  

 {0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address already in use 
(98)
   98.951201
  = bluetoothd: Failed to create GATT database for adapter  

  [hci0] 

[Touch-packages] [Bug 1962769] Lsusb.txt

2022-03-02 Thread Rabee
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1962769/+attachment/5565121/+files/Lsusb.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769

Title:
  Could not receive advertising events: Broken pipe

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  If a host has 2 adapters, the scanner run for a few second then get an
  error msg Could not receive advertising events: Broken pipe, then hci0
  turns down when I run hciconfig

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  DOWN
  RX bytes:574 acl:0 sco:0 events:30 errors:0
  TX bytes:368 acl:0 sco:0 commands:30 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221883 acl:0 sco:0 events:8327 errors:0
  TX bytes:1027 acl:0 sco:0 commands:67 errors:0

  
  This happend after I updated bluez from 5.62 to 5.63.

  If I do scan again, everything works fine with one adapter.

  
  As both adapters use the same mac address, I changed the address of hci0

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:01:07:00:47:0E  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:1184 acl:0 sco:0 events:66 errors:0
  TX bytes:1072 acl:0 sco:0 commands:66 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221961 acl:0 sco:0 events:8340 errors:0
  TX bytes:3078 acl:0 sco:0 commands:80 errors:0

  
  but the old address keeps reverted back which was not the case in 5.62

  I ran scan again while running btmon

  @ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0] 
1052.238244
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address al..   
1052.238720
  = bluetoothd: Failed to create GATT database for adapter [hci0] 
1052.238742
  = bluetoothd: Unable to register new adapter [hci0] 
1052.238761
  = Close Index: 00:1A:7D:DA:71:13 [hci0] 
1054.246981

  @ MGMT Event: Index Added (0x0004) plen 0 

 {0x0001} [hci0] 98.950611
  @ MGMT Command: Read Controller Information (0x0004) plen 0   

 {0x0001} [hci0] 98.950707
  @ MGMT Event: Command Complete (0x0001) plen 283  

 {0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address already in use 
(98)
   98.951201
  = bluetoothd: Failed to create GATT database for adapter  

  [hci0] 98.951229
  = 

[Touch-packages] [Bug 1962769] Lspci.txt

2022-03-02 Thread Rabee
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1962769/+attachment/5565119/+files/Lspci.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769

Title:
  Could not receive advertising events: Broken pipe

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  If a host has 2 adapters, the scanner run for a few second then get an
  error msg Could not receive advertising events: Broken pipe, then hci0
  turns down when I run hciconfig

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  DOWN
  RX bytes:574 acl:0 sco:0 events:30 errors:0
  TX bytes:368 acl:0 sco:0 commands:30 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221883 acl:0 sco:0 events:8327 errors:0
  TX bytes:1027 acl:0 sco:0 commands:67 errors:0

  
  This happend after I updated bluez from 5.62 to 5.63.

  If I do scan again, everything works fine with one adapter.

  
  As both adapters use the same mac address, I changed the address of hci0

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:01:07:00:47:0E  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:1184 acl:0 sco:0 events:66 errors:0
  TX bytes:1072 acl:0 sco:0 commands:66 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221961 acl:0 sco:0 events:8340 errors:0
  TX bytes:3078 acl:0 sco:0 commands:80 errors:0

  
  but the old address keeps reverted back which was not the case in 5.62

  I ran scan again while running btmon

  @ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0] 
1052.238244
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address al..   
1052.238720
  = bluetoothd: Failed to create GATT database for adapter [hci0] 
1052.238742
  = bluetoothd: Unable to register new adapter [hci0] 
1052.238761
  = Close Index: 00:1A:7D:DA:71:13 [hci0] 
1054.246981

  @ MGMT Event: Index Added (0x0004) plen 0 

 {0x0001} [hci0] 98.950611
  @ MGMT Command: Read Controller Information (0x0004) plen 0   

 {0x0001} [hci0] 98.950707
  @ MGMT Event: Command Complete (0x0001) plen 283  

 {0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address already in use 
(98)
   98.951201
  = bluetoothd: Failed to create GATT database for adapter  

  [hci0] 98.951229
  = 

[Touch-packages] [Bug 1962769] Re: Could not receive advertising events: Broken pipe

2022-03-02 Thread Rabee
apport information

** Tags added: apport-collected focal uec-images

** Description changed:

  If a host has 2 adapters, the scanner run for a few second then get an
  error msg Could not receive advertising events: Broken pipe, then hci0
  turns down when I run hciconfig
  
  hci0:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  DOWN
  RX bytes:574 acl:0 sco:0 events:30 errors:0
  TX bytes:368 acl:0 sco:0 commands:30 errors:0
  
  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221883 acl:0 sco:0 events:8327 errors:0
  TX bytes:1027 acl:0 sco:0 commands:67 errors:0
  
  
  This happend after I updated bluez from 5.62 to 5.63.
  
  If I do scan again, everything works fine with one adapter.
  
  
  As both adapters use the same mac address, I changed the address of hci0
  
  hci0:   Type: Primary  Bus: USB
  BD Address: 00:01:07:00:47:0E  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:1184 acl:0 sco:0 events:66 errors:0
  TX bytes:1072 acl:0 sco:0 commands:66 errors:0
  
  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221961 acl:0 sco:0 events:8340 errors:0
  TX bytes:3078 acl:0 sco:0 commands:80 errors:0
  
  
  but the old address keeps reverted back which was not the case in 5.62
  
  I ran scan again while running btmon
  
  @ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0] 
1052.238244
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address al..   
1052.238720
  = bluetoothd: Failed to create GATT database for adapter [hci0] 
1052.238742
  = bluetoothd: Unable to register new adapter [hci0] 
1052.238761
  = Close Index: 00:1A:7D:DA:71:13 [hci0] 
1054.246981
  
  @ MGMT Event: Index Added (0x0004) plen 0 

 {0x0001} [hci0] 98.950611
  @ MGMT Command: Read Controller Information (0x0004) plen 0   

 {0x0001} [hci0] 98.950707
  @ MGMT Event: Command Complete (0x0001) plen 283  

 {0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address already in use 
(98)
   98.951201
  = bluetoothd: Failed to create GATT database for adapter  

  [hci0] 98.951229
  = bluetoothd: Unable to register new adapter  

  [hci0] 98.951248
  = Close Index: 00:1A:7D:DA:71:13  
 

[Touch-packages] [Bug 1962563] Re: bluetoothd crashed with SIGSEGV in __strlen_avx2() from _dbus_string_init_const() from _dbus_check_is_valid_path() from _dbus_check_is_valid_path() from dbus_message

2022-03-02 Thread Daniel van Vugt
The fix for #272 is included in:

bluez (5.63-0ubuntu2) jammy; urgency=medium

  * Cherry-pick 3 patches to fix some crash & reconnect issues
(LP: #1962542)

 -- Jeremy Bicha   Wed, 02 Mar 2022 10:26:23
+0100


** Changed in: bluez (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962563

Title:
  bluetoothd crashed with SIGSEGV in __strlen_avx2() from
  _dbus_string_init_const() from _dbus_check_is_valid_path() from
  _dbus_check_is_valid_path() from dbus_message_iter_append_basic()

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
bluez.  This problem was most recently seen with package version 5.63-0ubuntu1, 
the problem page at 
https://errors.ubuntu.com/problem/05251767678452859eebd21c29df5e7c4b67ff66 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1962563/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1962769] Re: Could not receive advertising events: Broken pipe

2022-03-02 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

  apport-collect 1962769

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Changed in: bluez (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962769

Title:
  Could not receive advertising events: Broken pipe

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  If a host has 2 adapters, the scanner run for a few second then get an
  error msg Could not receive advertising events: Broken pipe, then hci0
  turns down when I run hciconfig

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  DOWN
  RX bytes:574 acl:0 sco:0 events:30 errors:0
  TX bytes:368 acl:0 sco:0 commands:30 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221883 acl:0 sco:0 events:8327 errors:0
  TX bytes:1027 acl:0 sco:0 commands:67 errors:0

  
  This happend after I updated bluez from 5.62 to 5.63.

  If I do scan again, everything works fine with one adapter.

  
  As both adapters use the same mac address, I changed the address of hci0

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:01:07:00:47:0E  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:1184 acl:0 sco:0 events:66 errors:0
  TX bytes:1072 acl:0 sco:0 commands:66 errors:0

  hci1:   Type: Primary  Bus: USB
  BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
  UP RUNNING
  RX bytes:221961 acl:0 sco:0 events:8340 errors:0
  TX bytes:3078 acl:0 sco:0 commands:80 errors:0

  
  but the old address keeps reverted back which was not the case in 5.62

  I ran scan again while running btmon

  @ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0] 
1052.238244
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start listening: l2cap_bind: Address al..   
1052.238720
  = bluetoothd: Failed to create GATT database for adapter [hci0] 
1052.238742
  = bluetoothd: Unable to register new adapter [hci0] 
1052.238761
  = Close Index: 00:1A:7D:DA:71:13 [hci0] 
1054.246981

  @ MGMT Event: Index Added (0x0004) plen 0 

 {0x0001} [hci0] 98.950611
  @ MGMT Command: Read Controller Information (0x0004) plen 0   

 {0x0001} [hci0] 98.950707
  @ MGMT Event: Command Complete (0x0001) plen 283  

 {0x0001} [hci0] 98.950714
Read Controller Information (0x0004) plen 280
  Status: Success (0x00)
  Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
  Version: Bluetooth 4.0 (0x06)
  Manufacturer: Cambridge Silicon Radio (10)
  Supported settings: 0x0001beff
Powered
Connectable
Fast Connectable
Discoverable
Bondable
Link Security
Secure Simple Pairing
BR/EDR
Low Energy
Advertising
Secure Connections
Debug Keys
Privacy
Static Address
PHY Configuration
  Current settings: 0x0080
BR/EDR
  Class: 0x00
Major class: Miscellaneous
Minor class: 0x00
  Name: CSR8510 A10
  Short name:
  = bluetoothd: Failed to start 

[Touch-packages] [Bug 1962789] [NEW] e2fsck crashes with Signal (11) SIGSEGV when using undo-file

2022-03-02 Thread Felix E
Public bug reported:

The behavior is reproducable on 18.04 and 20.04 LTS with the following versions 
of e2fsck:
* e2fsck 1.44.1 (24-Mar-2018)
* e2fsck 1.45.5 (07-Jan-2020)


Expected behavior occurs when:
* Running e2fsck as a dry run does work fine: It does find quite a few errors 
and then completes execution normally
* Running e2fsck "normally" (without an undo-file) works also fine - but I 
aborted execution at the first error it found (I want to use the undo file).

The error occurs reproducable when I specify an undo-file.
The error occurs on Ubuntu 18.04 and 20.04 as well.
The stack trace (see below) is identical when I repeat the execution.

As someone guessed that a lack of RAM might cause this I also observed
the process in top: It shows e2fsck running with 100% CPU and ~1% of RAM
for a few seconds, then it terminates with Signal (11).


Stacktrace with Ubuntu 18.04:

# e2fsck -v -z /root/e2fsck.undo_2022-03-01_15.00 /dev/mapper/md125_crypt
e2fsck 1.44.1 (24-Mar-2018)
Overwriting existing filesystem; this can be undone using the command:
e2undo /root/e2fsck.undo_2022-03-01_15.00 /dev/mapper/md125_crypt

ext2fs_check_desc: Corrupt group descriptor: bad block for block bitmap
e2fsck: Group descriptors look bad... trying backup blocks...
Signal (11) SIGSEGV si_code=SEGV_MAPERR fault addr=0x178
e2fsck(+0x30d29)[0x55a7f46c4d29]
/lib/x86_64-linux-gnu/libc.so.6(+0x3f040)[0x7f091f069040]
/lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_close2+0x134)[0x7f091fc93534]
/lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_close_free+0x16)[0x7f091fc93596]
e2fsck(main+0x65d)[0x55a7f46a310d]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7f091f04bbf7]
e2fsck(_start+0x2a)[0x55a7f46a5afa]


Stacktrace with Ubuntu 20.04 (I did an dist-upgrade from 18 to 20 in the hope 
that this issue might have been fixed there..):

# fsck.ext4 -v -z /root/fsck.ext4.undo_2022-03-01_17.53 /dev/mapper/md125_crypt
e2fsck 1.45.5 (07-Jan-2020)
Overwriting existing filesystem; this can be undone using the command:
e2undo /root/fsck.ext4.undo_2022-03-01_17.53 /dev/mapper/md125_crypt

ext2fs_check_desc: Corrupt group descriptor: bad block for block bitmap
fsck.ext4: Group descriptors look bad... trying backup blocks...
Signal (11) SIGSEGV si_code=SEGV_MAPERR fault addr=0x178
fsck.ext4(+0x34c21)[0x55d447822c21]
/lib/x86_64-linux-gnu/libc.so.6(+0x46210)[0x7f81371d6210]
/lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_close2+0x15c)[0x7f813740c6dc]
/lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_close_free+0x1a)[0x7f813740c71a]
fsck.ext4(main+0x12a2)[0x55d4477ffe22]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0x7f81371b70b3]
fsck.ext4(_start+0x2e)[0x55d4478020be]


Background-Info:
On 18.04:
A filesystem with ~66 TB was to be resized (resize2fs) to ~77TB.
Unfortunately I shut down the box while the resize was still running by 
accident (don't ask...)
After booting up again a run of e2fsck found and fixed some errors (a few Block 
bitmap differences and one occurrence of free block count and free inodes 
counts each.
A second run of e2fsck came clean.
The files inside the filesystem were fine (I had a sfv-file for a major part of 
the data inside).
Then I started resize2fs again, as the FS had only grown to ~70 TB so far.
Now i got a myriad of errors like 
> Illegal block number passed to ext2fs_mark_block_bitmap #17446378287038201972 
> for copy of block bitmap for /dev
and possibly other errors as well which had scrolled outside of my screen.
Then it finally completed with
> The filesystem on /dev/mapper/md125_crypt is now 20507814912 (4k) blocks long.

Now I'm trying to fix things but as I get errors like 
> Inode table for group 585696 is not in group.  (block 17480552796351627264)
> WARNING: SEVERE DATA LOSS POSSIBLE.
> Relocate?
I really would prefer to proceed with an undo-file now.

** Affects: e2fsprogs (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1962789

Title:
  e2fsck crashes with Signal (11) SIGSEGV when using undo-file

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  The behavior is reproducable on 18.04 and 20.04 LTS with the following 
versions of e2fsck:
  * e2fsck 1.44.1 (24-Mar-2018)
  * e2fsck 1.45.5 (07-Jan-2020)

  
  Expected behavior occurs when:
  * Running e2fsck as a dry run does work fine: It does find quite a few errors 
and then completes execution normally
  * Running e2fsck "normally" (without an undo-file) works also fine - but I 
aborted execution at the first error it found (I want to use the undo file).

  The error occurs reproducable when I specify an undo-file.
  The error occurs on Ubuntu 18.04 and 20.04 as well.
  The stack trace (see below) is identical when I repeat the execution.

  As someone guessed that a lack of RAM might cause this I also observed
  the process in top: It shows e2fsck 

[Touch-packages] [Bug 1962780] Re: During install "error processing package libglib2.0-0:i386"

2022-03-02 Thread Ralph
I tried to fix it

ralph@toumeya:~/Desktop$  sudo dpkg --configure -a 
ralph@toumeya:~/Desktop$ sudo apt-get install -f
Reading package lists... Done
Building dependency tree   
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.


and it appears that nothing happened??

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1962780

Title:
  During install  "error processing package libglib2.0-0:i386"

Status in glib2.0 package in Ubuntu:
  Invalid

Bug description:
  Installing the update for libglib2.0-0:i386 fails on two different computers.
  Output follows for the update.  The errors are near the bottom.  

  Other requested info is at the bottom.

  (Reading database ... 446385 files and directories currently installed.)
  Preparing to unpack .../0-libc6-i386_2.31-0ubuntu9.7_amd64.deb ...
  Unpacking libc6-i386 (2.31-0ubuntu9.7) over (2.31-0ubuntu9.3) ...
  Replaced by files in installed package libc6:i386 (2.31-0ubuntu9.3) ...
  Preparing to unpack .../1-libc6-dev_2.31-0ubuntu9.7_amd64.deb ...
  Unpacking libc6-dev:amd64 (2.31-0ubuntu9.7) over (2.31-0ubuntu9.3) ...
  Preparing to unpack .../2-libc-dev-bin_2.31-0ubuntu9.7_amd64.deb ...
  Unpacking libc-dev-bin (2.31-0ubuntu9.7) over (2.31-0ubuntu9.3) ...
  Preparing to unpack .../3-libc6-dbg_2.31-0ubuntu9.7_amd64.deb ...
  Unpacking libc6-dbg:amd64 (2.31-0ubuntu9.7) over (2.31-0ubuntu9.3) ...
  Preparing to unpack .../4-libc6_2.31-0ubuntu9.7_i386.deb ...
  De-configuring libc6:amd64 (2.31-0ubuntu9.3) ...
  Unpacking libc6:i386 (2.31-0ubuntu9.7) over (2.31-0ubuntu9.3) ...
  Preparing to unpack .../5-libc6_2.31-0ubuntu9.7_amd64.deb ...
  Unpacking libc6:amd64 (2.31-0ubuntu9.7) over (2.31-0ubuntu9.3) ...
  Setting up libc6:amd64 (2.31-0ubuntu9.7) ...
  (Reading database ... 446385 files and directories currently installed.)
  Preparing to unpack .../locales_2.31-0ubuntu9.7_all.deb ...
  Unpacking locales (2.31-0ubuntu9.7) over (2.31-0ubuntu9.3) ...
  Preparing to unpack .../libc-bin_2.31-0ubuntu9.7_amd64.deb ...
  Unpacking libc-bin (2.31-0ubuntu9.7) over (2.31-0ubuntu9.3) ...
  Setting up libc-bin (2.31-0ubuntu9.7) ...
  (Reading database ... 446385 files and directories currently installed.)
  Preparing to unpack .../libgtk-3-common_3.24.20-0ubuntu1.1_all.deb ...
  Unpacking libgtk-3-common (3.24.20-0ubuntu1.1) over (3.24.20-0ubuntu1) ...
  Setting up libgtk-3-common (3.24.20-0ubuntu1.1) ...
  (Reading database ... 446385 files and directories currently installed.)
  Preparing to unpack .../libgail-3-0_3.24.20-0ubuntu1.1_amd64.deb ...
  Unpacking libgail-3-0:amd64 (3.24.20-0ubuntu1.1) over (3.24.20-0ubuntu1) ...
  Preparing to unpack .../libgtk-3-0_3.24.20-0ubuntu1.1_amd64.deb ...
  Unpacking libgtk-3-0:amd64 (3.24.20-0ubuntu1.1) over (3.24.20-0ubuntu1) ...
  dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386:
   libglib2.0-0:i386 depends on libc6 (>= 2.28); however:
Package libc6:i386 is not configured yet.

  dpkg: error processing package libglib2.0-0:i386 (--configure):
   dependency problems - leaving triggers unprocessed
  dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386:
   libglib2.0-0:i386 depends on libc6 (>= 2.28); however:
Package libc6:i386 is not configured yet.

  dpkg: error processing package libglib2.0-0:i386 (--configure):
   dependency problems - leaving triggers unprocessed
  dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386:
   libglib2.0-0:i386 depends on libc6 (>= 2.28); however:
Package libc6:i386 is not configured yet.

  dpkg: error processing package libglib2.0-0:i386 (--configure):
   dependency problems - leaving triggers unprocessed
  dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386:
   libglib2.0-0:i386 depends on libc6 (>= 2.28); however:
Package libc6:i386 is not configured yet.

  dpkg: error processing package libglib2.0-0:i386 (--configure):
   dependency problems - leaving triggers unprocessed
  No apport report written because MaxReports is reached already

  and this goes on for a VERY long time!  It hangs the package manager!
  Full output is attached.

  
  I am using Linux Mint 20.3

  ralph@toumeya:~/Desktop$ sudo apt-cache policy libglib2.0-0:i386
  libglib2.0-0:i386:
Installed: 2.64.6-1~ubuntu20.04.4
Candidate: 2.64.6-1~ubuntu20.04.4
Version table:
   *** 2.64.6-1~ubuntu20.04.4 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main i386 Packages
  100 /var/lib/dpkg/status
   2.64.6-1~ubuntu20.04.3 500
  500 http://security.ubuntu.com/ubuntu focal-security/main i386 
Packages
   2.64.2-1~fakesync1 500
  500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages
  ralph@toumeya:~/Desktop$ 

  
  I expect the install to occur with NO errors!

  Questions?? Drop me a 

[Touch-packages] [Bug 1962780] Re: During install "error processing package libglib2.0-0:i386"

2022-03-02 Thread Sebastien Bacher
Thanks but you should report those issues to Mint since that's the
distribution you are using

** Changed in: glib2.0 (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1962780

Title:
  During install  "error processing package libglib2.0-0:i386"

Status in glib2.0 package in Ubuntu:
  Invalid

Bug description:
  Installing the update for libglib2.0-0:i386 fails on two different computers.
  Output follows for the update.  The errors are near the bottom.  

  Other requested info is at the bottom.

  (Reading database ... 446385 files and directories currently installed.)
  Preparing to unpack .../0-libc6-i386_2.31-0ubuntu9.7_amd64.deb ...
  Unpacking libc6-i386 (2.31-0ubuntu9.7) over (2.31-0ubuntu9.3) ...
  Replaced by files in installed package libc6:i386 (2.31-0ubuntu9.3) ...
  Preparing to unpack .../1-libc6-dev_2.31-0ubuntu9.7_amd64.deb ...
  Unpacking libc6-dev:amd64 (2.31-0ubuntu9.7) over (2.31-0ubuntu9.3) ...
  Preparing to unpack .../2-libc-dev-bin_2.31-0ubuntu9.7_amd64.deb ...
  Unpacking libc-dev-bin (2.31-0ubuntu9.7) over (2.31-0ubuntu9.3) ...
  Preparing to unpack .../3-libc6-dbg_2.31-0ubuntu9.7_amd64.deb ...
  Unpacking libc6-dbg:amd64 (2.31-0ubuntu9.7) over (2.31-0ubuntu9.3) ...
  Preparing to unpack .../4-libc6_2.31-0ubuntu9.7_i386.deb ...
  De-configuring libc6:amd64 (2.31-0ubuntu9.3) ...
  Unpacking libc6:i386 (2.31-0ubuntu9.7) over (2.31-0ubuntu9.3) ...
  Preparing to unpack .../5-libc6_2.31-0ubuntu9.7_amd64.deb ...
  Unpacking libc6:amd64 (2.31-0ubuntu9.7) over (2.31-0ubuntu9.3) ...
  Setting up libc6:amd64 (2.31-0ubuntu9.7) ...
  (Reading database ... 446385 files and directories currently installed.)
  Preparing to unpack .../locales_2.31-0ubuntu9.7_all.deb ...
  Unpacking locales (2.31-0ubuntu9.7) over (2.31-0ubuntu9.3) ...
  Preparing to unpack .../libc-bin_2.31-0ubuntu9.7_amd64.deb ...
  Unpacking libc-bin (2.31-0ubuntu9.7) over (2.31-0ubuntu9.3) ...
  Setting up libc-bin (2.31-0ubuntu9.7) ...
  (Reading database ... 446385 files and directories currently installed.)
  Preparing to unpack .../libgtk-3-common_3.24.20-0ubuntu1.1_all.deb ...
  Unpacking libgtk-3-common (3.24.20-0ubuntu1.1) over (3.24.20-0ubuntu1) ...
  Setting up libgtk-3-common (3.24.20-0ubuntu1.1) ...
  (Reading database ... 446385 files and directories currently installed.)
  Preparing to unpack .../libgail-3-0_3.24.20-0ubuntu1.1_amd64.deb ...
  Unpacking libgail-3-0:amd64 (3.24.20-0ubuntu1.1) over (3.24.20-0ubuntu1) ...
  Preparing to unpack .../libgtk-3-0_3.24.20-0ubuntu1.1_amd64.deb ...
  Unpacking libgtk-3-0:amd64 (3.24.20-0ubuntu1.1) over (3.24.20-0ubuntu1) ...
  dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386:
   libglib2.0-0:i386 depends on libc6 (>= 2.28); however:
Package libc6:i386 is not configured yet.

  dpkg: error processing package libglib2.0-0:i386 (--configure):
   dependency problems - leaving triggers unprocessed
  dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386:
   libglib2.0-0:i386 depends on libc6 (>= 2.28); however:
Package libc6:i386 is not configured yet.

  dpkg: error processing package libglib2.0-0:i386 (--configure):
   dependency problems - leaving triggers unprocessed
  dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386:
   libglib2.0-0:i386 depends on libc6 (>= 2.28); however:
Package libc6:i386 is not configured yet.

  dpkg: error processing package libglib2.0-0:i386 (--configure):
   dependency problems - leaving triggers unprocessed
  dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386:
   libglib2.0-0:i386 depends on libc6 (>= 2.28); however:
Package libc6:i386 is not configured yet.

  dpkg: error processing package libglib2.0-0:i386 (--configure):
   dependency problems - leaving triggers unprocessed
  No apport report written because MaxReports is reached already

  and this goes on for a VERY long time!  It hangs the package manager!
  Full output is attached.

  
  I am using Linux Mint 20.3

  ralph@toumeya:~/Desktop$ sudo apt-cache policy libglib2.0-0:i386
  libglib2.0-0:i386:
Installed: 2.64.6-1~ubuntu20.04.4
Candidate: 2.64.6-1~ubuntu20.04.4
Version table:
   *** 2.64.6-1~ubuntu20.04.4 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main i386 Packages
  100 /var/lib/dpkg/status
   2.64.6-1~ubuntu20.04.3 500
  500 http://security.ubuntu.com/ubuntu focal-security/main i386 
Packages
   2.64.2-1~fakesync1 500
  500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages
  ralph@toumeya:~/Desktop$ 

  
  I expect the install to occur with NO errors!

  Questions?? Drop me a note!  I have been using Debian distributions for 15+ 
years.
  Ralph

To manage notifications about this bug go to:

[Touch-packages] [Bug 1962780] [NEW] During install "error processing package libglib2.0-0:i386"

2022-03-02 Thread Ralph
Public bug reported:

Installing the update for libglib2.0-0:i386 fails on two different computers.
Output follows for the update.  The errors are near the bottom.  

Other requested info is at the bottom.

(Reading database ... 446385 files and directories currently installed.)
Preparing to unpack .../0-libc6-i386_2.31-0ubuntu9.7_amd64.deb ...
Unpacking libc6-i386 (2.31-0ubuntu9.7) over (2.31-0ubuntu9.3) ...
Replaced by files in installed package libc6:i386 (2.31-0ubuntu9.3) ...
Preparing to unpack .../1-libc6-dev_2.31-0ubuntu9.7_amd64.deb ...
Unpacking libc6-dev:amd64 (2.31-0ubuntu9.7) over (2.31-0ubuntu9.3) ...
Preparing to unpack .../2-libc-dev-bin_2.31-0ubuntu9.7_amd64.deb ...
Unpacking libc-dev-bin (2.31-0ubuntu9.7) over (2.31-0ubuntu9.3) ...
Preparing to unpack .../3-libc6-dbg_2.31-0ubuntu9.7_amd64.deb ...
Unpacking libc6-dbg:amd64 (2.31-0ubuntu9.7) over (2.31-0ubuntu9.3) ...
Preparing to unpack .../4-libc6_2.31-0ubuntu9.7_i386.deb ...
De-configuring libc6:amd64 (2.31-0ubuntu9.3) ...
Unpacking libc6:i386 (2.31-0ubuntu9.7) over (2.31-0ubuntu9.3) ...
Preparing to unpack .../5-libc6_2.31-0ubuntu9.7_amd64.deb ...
Unpacking libc6:amd64 (2.31-0ubuntu9.7) over (2.31-0ubuntu9.3) ...
Setting up libc6:amd64 (2.31-0ubuntu9.7) ...
(Reading database ... 446385 files and directories currently installed.)
Preparing to unpack .../locales_2.31-0ubuntu9.7_all.deb ...
Unpacking locales (2.31-0ubuntu9.7) over (2.31-0ubuntu9.3) ...
Preparing to unpack .../libc-bin_2.31-0ubuntu9.7_amd64.deb ...
Unpacking libc-bin (2.31-0ubuntu9.7) over (2.31-0ubuntu9.3) ...
Setting up libc-bin (2.31-0ubuntu9.7) ...
(Reading database ... 446385 files and directories currently installed.)
Preparing to unpack .../libgtk-3-common_3.24.20-0ubuntu1.1_all.deb ...
Unpacking libgtk-3-common (3.24.20-0ubuntu1.1) over (3.24.20-0ubuntu1) ...
Setting up libgtk-3-common (3.24.20-0ubuntu1.1) ...
(Reading database ... 446385 files and directories currently installed.)
Preparing to unpack .../libgail-3-0_3.24.20-0ubuntu1.1_amd64.deb ...
Unpacking libgail-3-0:amd64 (3.24.20-0ubuntu1.1) over (3.24.20-0ubuntu1) ...
Preparing to unpack .../libgtk-3-0_3.24.20-0ubuntu1.1_amd64.deb ...
Unpacking libgtk-3-0:amd64 (3.24.20-0ubuntu1.1) over (3.24.20-0ubuntu1) ...
dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386:
 libglib2.0-0:i386 depends on libc6 (>= 2.28); however:
  Package libc6:i386 is not configured yet.

dpkg: error processing package libglib2.0-0:i386 (--configure):
 dependency problems - leaving triggers unprocessed
dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386:
 libglib2.0-0:i386 depends on libc6 (>= 2.28); however:
  Package libc6:i386 is not configured yet.

dpkg: error processing package libglib2.0-0:i386 (--configure):
 dependency problems - leaving triggers unprocessed
dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386:
 libglib2.0-0:i386 depends on libc6 (>= 2.28); however:
  Package libc6:i386 is not configured yet.

dpkg: error processing package libglib2.0-0:i386 (--configure):
 dependency problems - leaving triggers unprocessed
dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386:
 libglib2.0-0:i386 depends on libc6 (>= 2.28); however:
  Package libc6:i386 is not configured yet.

dpkg: error processing package libglib2.0-0:i386 (--configure):
 dependency problems - leaving triggers unprocessed
No apport report written because MaxReports is reached already

and this goes on for a VERY long time!  It hangs the package manager!
Full output is attached.


I am using Linux Mint 20.3

ralph@toumeya:~/Desktop$ sudo apt-cache policy libglib2.0-0:i386
libglib2.0-0:i386:
  Installed: 2.64.6-1~ubuntu20.04.4
  Candidate: 2.64.6-1~ubuntu20.04.4
  Version table:
 *** 2.64.6-1~ubuntu20.04.4 500
500 http://archive.ubuntu.com/ubuntu focal-updates/main i386 Packages
100 /var/lib/dpkg/status
 2.64.6-1~ubuntu20.04.3 500
500 http://security.ubuntu.com/ubuntu focal-security/main i386 Packages
 2.64.2-1~fakesync1 500
500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages
ralph@toumeya:~/Desktop$ 


I expect the install to occur with NO errors!

Questions?? Drop me a note!  I have been using Debian distributions for 15+ 
years.
Ralph

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: libglib2.0

** Attachment added: "Full output for FAILED install"
   
https://bugs.launchpad.net/bugs/1962780/+attachment/5565107/+files/PackageError.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1962780

Title:
  During install  "error processing package libglib2.0-0:i386"

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Installing the update for libglib2.0-0:i386 fails on two different computers.
  Output follows for the update.  The errors are near the 

[Touch-packages] [Bug 1958019]

2022-03-02 Thread ferkorol
Here is another variant, now with RC6, works the sound and the nvidia
drivers at the same time! (with some tricks):

A) FIRST TIME
1) install kernel build tools:
(https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel):

* sudo apt install libncurses-dev gawk flex bison openssl libssl-dev
dkms libelf-dev libudev-dev libpci-dev libiberty-dev autoconf git p7zip-
full

2) clone the kernel from github and checkout to v5.17 branch (Rather
large, multiple GB's):

* git clone https://github.com/torvalds/linux.git

3)Make a 7z of the linux folder in a clear state
7z a linux-clean.7z linux

3) get the patch and let it in one superior level of the linux folder:

https://patchwork.kernel.org/project/linux-
acpi/patch/20220121172431.6876-4-sbind...@opensource.cirrus.com/


A) FOR EACH RC RELEASE:
7z x linux-clean.7z
cp Support-Spi-in-i2c-multi-instantiate-driver.patch linux/
cd linux
git pull
git checkout v5.17-rc6
git am Support-Spi-in-i2c-multi-instantiate-driver.patch
make olddefconfig
./scripts/config --enable CONFIG_SERIAL_MULTI_INSTANTIATE
./scripts/config --enable CONFIG_SND_HDA_SCODEC_CS35L41_I2C
./scripts/config --enable CONFIG_SND_HDA_SCODEC_CS35L41_SPI
./scripts/config --disable CONFIG_DEBUG_INFO
./scripts/config --set-str CONFIG_SYSTEM_TRUSTED_KEYS ""
./scripts/config --set-str CONFIG_SYSTEM_REVOCATION_KEYS ""
make -j 16
make modules_install
make install


The patch is mandatory to enable the sound in ubuntu, im tried without the path 
and the sound don't work. With this steps will do.
In order to make work the nvidia drivers in the 17-rc6 im just change in "more 
drivers" option of ubuntu, the current versión of the nvidia driver for another 
(511 to 470 for example).
Im using hybrid graphics mode in the bios.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1958019

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1962769] [NEW] Could not receive advertising events: Broken pipe

2022-03-02 Thread Rabee
Public bug reported:

If a host has 2 adapters, the scanner run for a few second then get an
error msg Could not receive advertising events: Broken pipe, then hci0
turns down when I run hciconfig

hci0:   Type: Primary  Bus: USB
BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
DOWN
RX bytes:574 acl:0 sco:0 events:30 errors:0
TX bytes:368 acl:0 sco:0 commands:30 errors:0

hci1:   Type: Primary  Bus: USB
BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING
RX bytes:221883 acl:0 sco:0 events:8327 errors:0
TX bytes:1027 acl:0 sco:0 commands:67 errors:0


This happend after I updated bluez from 5.62 to 5.63.

If I do scan again, everything works fine with one adapter.


As both adapters use the same mac address, I changed the address of hci0

hci0:   Type: Primary  Bus: USB
BD Address: 00:01:07:00:47:0E  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING
RX bytes:1184 acl:0 sco:0 events:66 errors:0
TX bytes:1072 acl:0 sco:0 commands:66 errors:0

hci1:   Type: Primary  Bus: USB
BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING
RX bytes:221961 acl:0 sco:0 events:8340 errors:0
TX bytes:3078 acl:0 sco:0 commands:80 errors:0


but the old address keeps reverted back which was not the case in 5.62

I ran scan again while running btmon

@ MGMT Event: Command Complete (0x0001) plen 283{0x0001} [hci0] 1052.238244
  Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
  Powered
  Connectable
  Fast Connectable
  Discoverable
  Bondable
  Link Security
  Secure Simple Pairing
  BR/EDR
  Low Energy
  Advertising
  Secure Connections
  Debug Keys
  Privacy
  Static Address
  PHY Configuration
Current settings: 0x0080
  BR/EDR
Class: 0x00
  Major class: Miscellaneous
  Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address al..   1052.238720
= bluetoothd: Failed to create GATT database for adapter [hci0] 1052.238742
= bluetoothd: Unable to register new adapter [hci0] 1052.238761
= Close Index: 00:1A:7D:DA:71:13 [hci0] 1054.246981

@ MGMT Event: Index Added (0x0004) plen 0   

   {0x0001} [hci0] 98.950611
@ MGMT Command: Read Controller Information (0x0004) plen 0 

   {0x0001} [hci0] 98.950707
@ MGMT Event: Command Complete (0x0001) plen 283

   {0x0001} [hci0] 98.950714
  Read Controller Information (0x0004) plen 280
Status: Success (0x00)
Address: 00:1A:7D:DA:71:13 (cyber-blue(HK)Ltd)
Version: Bluetooth 4.0 (0x06)
Manufacturer: Cambridge Silicon Radio (10)
Supported settings: 0x0001beff
  Powered
  Connectable
  Fast Connectable
  Discoverable
  Bondable
  Link Security
  Secure Simple Pairing
  BR/EDR
  Low Energy
  Advertising
  Secure Connections
  Debug Keys
  Privacy
  Static Address
  PHY Configuration
Current settings: 0x0080
  BR/EDR
Class: 0x00
  Major class: Miscellaneous
  Minor class: 0x00
Name: CSR8510 A10
Short name:
= bluetoothd: Failed to start listening: l2cap_bind: Address already in use 
(98)
   98.951201
= bluetoothd: Failed to create GATT database for adapter

[hci0] 98.951229
= bluetoothd: Unable to register new adapter

[hci0] 98.951248
= Close Index: 00:1A:7D:DA:71:13

   [hci0] 100.967001

** Affects: bluez (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.

[Touch-packages] [Bug 1962453] Re: Apply default TTL to records obtained from getaddrinfo()

2022-03-02 Thread Robie Basak
> [Test plan]

Please could you add to the test plan testing to ensure that the new
configurable timeout actually works? There's a lot of code being added
just to make this configurable, including an entirely new configuration
file and extensive by-hand C parsing code. I think we should ensure that
this code actually works - otherwise I don't think including it all is
justified.

> [Where problems could occur]

Am I right in thinking that it will no longer be possible to set an
infinite lifetime, even by configuration? If we can't think of any case
where a user would want this then I think it's fine to proceed as-is,
but it's worth calling it out as a place where problems might occur.

--

One minor issue that's maybe worth fixing before landing this: the new
manpage (including upstream) refers to a different configuration file
path than where the code actually looks. Please could you patch to make
them match - including in Jammy? Otherwise we rather defeat the point of
including the new manpage in this SRU.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to keyutils in Ubuntu.
https://bugs.launchpad.net/bugs/1962453

Title:
  Apply default TTL to records obtained from getaddrinfo()

Status in keyutils package in Ubuntu:
  Fix Released
Status in keyutils source package in Focal:
  New
Status in keyutils source package in Impish:
  New

Bug description:
  [Impact]
  

  There's a strong dependency for cifs.ko (and nfs.ko) on keyutils for
  DNS resolution. The keyutils package contains the userspace utility to
  update the kernel keyring with the DNS mapping to IP address. Prior to
  1.6.2, this utility may erroneously set unlimited lifetime for this
  keyring in the kernel.

  [Test plan]
  ===

  1. Create a file share on an SMB server (can be a samba server) with
  two IP addresses. Make sure that FQDN of the server resolves to one of
  these addresses.

  2. mount the created share on the cifs client using the FQDN for the
  server. Make sure that the mount point is accessible.

  3. Using the ss command on the client, to kill the sockets that
  connect to the server: sudo ss -K dport :445

  4. Now update the DNS entry to make sure that the server FQDN now
  resolves to the second IP address of the server. Make sure that
  nslookup on the client now resolves to the new IP address.

  5. Repeat step 3 to kill the sockets that connect to server to force
  re-connection again.

  Without the fix, after step 5, with the "ss -t" command, you'll see
  that the client has reconnected to the old IP address, even when DNS
  lookups return the new IP.

  With the fix (after a reboot of the client machine to make sure that
  kernel keys are refreshed), you'll see that the client reconnects to
  the new IP address.

  The bug is due to unlimited lifetime set by key.dns_resolver (which is
  part of keyutils package). As a result, even if IP address for the DNS
  entries change, the kernel filesystems would continue to use old IP
  address, due to the cached keys. This issue causes clients to
  misbehave when Azure Files service endpoints move to a different
  cluster.

  [Where problems could occur]
  

  Address records obtained from getaddrinfo() don't come with any TTL
  information, even if they're obtained from the DNS, so if someone is
  relying on this particularly, might face some problem/regression but I
  don't think they would face that as it would still be highly
  configurable.

  [Other information]
  ===

  This request is essentially from one of our cloud partners and they're
  highly affected by this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1962453/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1947200] Re: [i965] enable Gallium3D crocus driver

2022-03-02 Thread Launchpad Bug Tracker
This bug was fixed in the package mesa - 21.3.5-1ubuntu1

---
mesa (21.3.5-1ubuntu1) jammy; urgency=medium

  * Revert back to llvm-12, again.

 -- Timo Aaltonen   Wed, 09 Feb 2022 10:19:02 +0200

** Changed in: mesa (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1947200

Title:
  [i965] enable Gallium3D crocus driver

Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  Starting with Mesa 21.2 an alternative driver for Intel hardware for
  Gen4 through Gen7 is available that is based on Gallium3D.

  It provides new features (like the Gallium Nine state tracker) and
  improved performance in some scenarios. Since the driver is still
  experimental, it is no enabled by default but can be selected by
  setting the

  MESA_LOADER_DRIVER_OVERRIDE=crocus

  environment variable.

  Ubuntu does not enable the driver in it's mesa build, when selected I
  will just get this error message instead:

  $ MESA_LOADER_DRIVER_OVERRIDE=crocus glxinfo
  libGL error: MESA-LOADER: failed to open crocus: /usr/lib/dri/crocus_dri.so: 
cannot open shared object file: No such file or directory (search paths 
/usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
  libGL error: failed to load driver: crocus
  libGL error: MESA-LOADER: failed to open crocus: /usr/lib/dri/crocus_dri.so: 
cannot open shared object file: No such file or directory (search paths 
/usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
  libGL error: failed to load driver: crocus

  
  This is with Mesa 21.2.2 - libgl1-mesa-dri (21.2.2-1ubuntu1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1947200/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network eduroam

2022-03-02 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1958267

** Tags added: iso-testing

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1958267

Title:
  "Connection failed" for WPA Enterprise network eduroam

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases

2022-03-02 Thread Robie Basak
** Changed in: klibc (Ubuntu Bionic)
   Status: In Progress => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/bugs/1947099

Title:
  ipconfig does not honour user-requested timeouts in some cases

Status in klibc package in Ubuntu:
  New
Status in klibc source package in Bionic:
  Incomplete

Bug description:
  
  [Impact]
  In some cases, ipconfig can take a longer time than the user-specified 
timeouts, causing unexpected delays.

  [Test Plan]
  Any situation where ipconfig encounters an error sending the DHCP packet, it 
will automatically set a delay of 10 seconds, which could be longer than the 
user-specified timeout. It can be reproduced by creating a dummy interface and 
attempting to run ipconfig on it with a timeout value of less than 10:

  # ip link add eth1 type dummy
  # date; /usr/lib/klibc/bin/ipconfig -t 2 eth1; date
  Thu Nov 18 04:46:13 EST 2021
  IP-Config: eth1 hardware address ae:e0:f5:9d:7e:00 mtu 1500 DHCP RARP
  IP-Config: no response after 2 secs - giving up
  Thu Nov 18 04:46:23 EST 2021

  ^ Notice above, ipconfig thinks that it waited 2 seconds, but the
  timestamps show an actual delay of 10 seconds.

  [Where problems could occur]
  Please see reproduction steps above. We are seeing this in production too 
(see comment #2).

  [Other Info]
  A patch to fix the issue is being proposed here. It is a safe fix - it only 
checks before going into sleep that the timeout never exceeds the 
user-requested value.

  [Original Description]

  In some cases, ipconfig can take longer than the user-specified
  timeouts, causing unexpected delays.

  in main.c, in function loop(), the process can go into
  process_timeout_event() (or process_receive_event() ) and if it
  encounters an error situation, will set an attempt to "try again
  later" at time equal now + 10 seconds by setting

  s->expire = now + 10;

  This can happen at any time during the main event loop, which can end
  up extending the user-specified timeout if "now + 10" is greater than
  "start_time + user-specified-timeout".

  I believe a patch like the following is needed to avoid this problem:

  --- a/usr/kinit/ipconfig/main.c
  +++ b/usr/kinit/ipconfig/main.c
  @@ -437,6 +437,13 @@ static int loop(void)

  if (timeout > s->expire - now.tv_sec)
  timeout = s->expire - now.tv_sec;
  +
  +   /* Compensate for already-lost time */
  +   gettimeofday(, NULL);
  +   if (now.tv_sec + timeout > start + loop_timeout) {
  +   timeout = loop_timeout - (now.tv_sec - start);
  +   printf("Lowered timeout to match user request 
= (%d s) \n", timeout);
  +   }
  }

  I believe the current behaviour is buggy. This is confirmed when the
  following line is executed:

  if (loop_timeout >= 0 &&
  now.tv_sec - start >= loop_timeout) {
  printf("IP-Config: no response after %d "
     "secs - giving up\n", loop_timeout);
  rc = -1;
  goto bail;
  }

  'loop_timeout' is the user-specified time-out. With a value of 2, in
  case of error, this line prints:

  IP-Config: no response after 2 secs - giving up

  So it thinks that it waited 2 seconds - however, in reality it had
  actually waited for 10 seconds.

  The suggested code-change ensures that the timeout that is actually
  used never exceeds the user-specified timeout.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1947099/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1962135] Re: [SRU] gstreamer 1.16.3 series

2022-03-02 Thread Jeremy Bicha
** Changed in: gst-plugins-bad1.0 (Ubuntu Focal)
   Status: In Progress => Triaged

** Changed in: gst-plugins-good1.0 (Ubuntu Focal)
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-base1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/1962135

Title:
  [SRU] gstreamer 1.16.3 series

Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 source package in Focal:
  Triaged
Status in gst-plugins-base1.0 source package in Focal:
  In Progress
Status in gst-plugins-good1.0 source package in Focal:
  In Progress
Status in gstreamer1.0 source package in Focal:
  In Progress

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.16 series
  that 20.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  If one of the fixes is bad then it might break video or audio
  playback, or could crash any application that tries to use gstreamer.

  ---


  On ubuntu-20.04 "apt-get" default installs gstreamer version 1.16.2,
  though gstreamer has subsequent minor version gst-1.16.3 with fixes
  incorporated.

  Hence, Ideally default gstreamer-1.16 minor version support with
  ubuntu-20.04 should be upgraded to use gstreamer version 1.16.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1962135/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1962542] Re: [jammy] Bluetooth headphones unable to connect after suspend in BlueZ 5.63

2022-03-02 Thread Daniel van Vugt
I expect this is https://github.com/bluez/bluez/issues/284 which Jeremy
is going to propose the patch for.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962542

Title:
  [jammy] Bluetooth headphones unable to connect after suspend in BlueZ
  5.63

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  Bose quietcomfort 35 is a common headset that can no longer connect to
  a jammy system after just one suspend. This started at the end of
  January but just now really debugging the issue.

  Side note that my bluetooth mouse works fine without problem after any
  amount of suspends.

  The headset is only trying to connect to the jammy system (no other
  bluetooth devices it's paired with has active bluetooth, to isolate
  only the jammy <-> headset issue). This is jammy running on a T590, up
  to date, not proposed.

  heather@fenrir:~$ dpkg -l | grep bluetooth
  ii  gir1.2-gnomebluetooth-1.0:amd643.34.5-4   
amd64Introspection data for GnomeBluetooth
  ii  gnome-bluetooth3.34.5-4   
amd64GNOME Bluetooth tools
  ii  libbluetooth-dev:amd64 5.63-0ubuntu1  
amd64Development files for using the BlueZ Linux Bluetooth 
library
  ii  libbluetooth3:amd645.63-0ubuntu1  
amd64Library to use the BlueZ Linux Bluetooth stack
  ii  libgnome-bluetooth13:amd64 3.34.5-4   
amd64GNOME Bluetooth tools - support library
  ii  pulseaudio-module-bluetooth1:15.99.1+dfsg1-1ubuntu1   
amd64Bluetooth module for PulseAudio sound server

  On a fresh boot (not suspended yet), I can connect the headset
  successfully. Here are the logs of that:

  Mar 01 09:44:02 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as 
/devices/virtual/input/input30
  Mar 01 09:44:02 fenrir systemd-logind[1570]: Watching system buttons on 
/dev/input/event22 (Bose QuietComfort 35 (AVRCP))
  Mar 01 09:44:03 fenrir NetworkManager[1536]:   [1646124243.8660] 
platform-linux: do-add-ip6-address[3: fe80::c1bc:a705:9e66:e0d0]: failure 13 
(Permission denied)
  Mar 01 09:44:04 fenrir bluetoothd[1532]: 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0: fd(32) ready
  Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 6 threads of 3 
processes of 1 users.
  Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Successfully made thread 5660 of 
process 2708 owned by '1000' RT at priority 5.
  Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 7 threads of 3 
processes of 1 users.
  Mar 01 09:44:04 fenrir pulseaudio[2708]: org.freedesktop.DBus.Properties.Get 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0 Volume failed: 
org.freedesktop.DBus.Error.InvalidArgs: No such property 'Volume'
  Mar 01 09:44:04 fenrir pulseaudio[2708]: Battery Level: 70%
  Mar 01 09:44:04 fenrir pulseaudio[2708]: Dock Status: undocked

  But then if I close the laptop lid and reopen, login, and try to
  connect the headset the device is found invalid with the following
  logs:

  Mar 01 00:47:08 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as 
/devices/virtual/input/input152
  Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
  Mar 01 00:47:08 fenrir bluetoothd[40741]: 
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
  Mar 01 00:47:08 fenrir bluetoothd[40741]: 
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 01 00:47:08 fenrir systemd-logind[1545]: Watching system buttons on 
/dev/input/event19 (Bose QuietComfort 35 (AVRCP))
  Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
  Mar 01 00:47:09 fenrir bluetoothd[40741]: 
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
  Mar 01 00:47:09 fenrir bluetoothd[40741]: 
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 01 00:47:09 fenrir pulseaudio[253956]: Device doesn't exist for 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F
  Mar 01 00:47:09 fenrir bluetoothd[40741]: src/profile.c:new_conn_reply() 
Hands-Free Voice gateway replied with an error: 
org.bluez.Error.InvalidArguments, Unable to handle new connection
  Mar 01 00:47:09 fenrir pulseaudio[253956]: Device doesn't 

[Touch-packages] [Bug 1962542] Re: [jammy] Bluetooth headphones unable to connect after suspend in BlueZ 5.63

2022-03-02 Thread Heather Ellsworth
Regarding comment #17 and missing devices from rfkill, there was just a
miscommunication. I meant that the bluetooth line has not changed, and
only pasted that one. But in both cases (before/after suspend), I do see
all three lines as mentioned in #17. Sorry for the unnecessary
confusion.

I'm also attaching a full journalctl -b0 log.

Then regarding https://github.com/bluez/bluez/issues/272 and
https://github.com/bluez/bluez/issues/220, I do not have a systemd
coredump so doesn't look like 272 directly. I could try to downgrade to
bluez 5.61 and see if that fixes the issue (I expect it does since it
was working fine till recently), but sounds like it's fixed in 5.64 so
I'll test this older version if really necessary :)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962542

Title:
  [jammy] Bluetooth headphones unable to connect after suspend in BlueZ
  5.63

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  Bose quietcomfort 35 is a common headset that can no longer connect to
  a jammy system after just one suspend. This started at the end of
  January but just now really debugging the issue.

  Side note that my bluetooth mouse works fine without problem after any
  amount of suspends.

  The headset is only trying to connect to the jammy system (no other
  bluetooth devices it's paired with has active bluetooth, to isolate
  only the jammy <-> headset issue). This is jammy running on a T590, up
  to date, not proposed.

  heather@fenrir:~$ dpkg -l | grep bluetooth
  ii  gir1.2-gnomebluetooth-1.0:amd643.34.5-4   
amd64Introspection data for GnomeBluetooth
  ii  gnome-bluetooth3.34.5-4   
amd64GNOME Bluetooth tools
  ii  libbluetooth-dev:amd64 5.63-0ubuntu1  
amd64Development files for using the BlueZ Linux Bluetooth 
library
  ii  libbluetooth3:amd645.63-0ubuntu1  
amd64Library to use the BlueZ Linux Bluetooth stack
  ii  libgnome-bluetooth13:amd64 3.34.5-4   
amd64GNOME Bluetooth tools - support library
  ii  pulseaudio-module-bluetooth1:15.99.1+dfsg1-1ubuntu1   
amd64Bluetooth module for PulseAudio sound server

  On a fresh boot (not suspended yet), I can connect the headset
  successfully. Here are the logs of that:

  Mar 01 09:44:02 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as 
/devices/virtual/input/input30
  Mar 01 09:44:02 fenrir systemd-logind[1570]: Watching system buttons on 
/dev/input/event22 (Bose QuietComfort 35 (AVRCP))
  Mar 01 09:44:03 fenrir NetworkManager[1536]:   [1646124243.8660] 
platform-linux: do-add-ip6-address[3: fe80::c1bc:a705:9e66:e0d0]: failure 13 
(Permission denied)
  Mar 01 09:44:04 fenrir bluetoothd[1532]: 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0: fd(32) ready
  Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 6 threads of 3 
processes of 1 users.
  Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Successfully made thread 5660 of 
process 2708 owned by '1000' RT at priority 5.
  Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 7 threads of 3 
processes of 1 users.
  Mar 01 09:44:04 fenrir pulseaudio[2708]: org.freedesktop.DBus.Properties.Get 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0 Volume failed: 
org.freedesktop.DBus.Error.InvalidArgs: No such property 'Volume'
  Mar 01 09:44:04 fenrir pulseaudio[2708]: Battery Level: 70%
  Mar 01 09:44:04 fenrir pulseaudio[2708]: Dock Status: undocked

  But then if I close the laptop lid and reopen, login, and try to
  connect the headset the device is found invalid with the following
  logs:

  Mar 01 00:47:08 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as 
/devices/virtual/input/input152
  Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
  Mar 01 00:47:08 fenrir bluetoothd[40741]: 
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
  Mar 01 00:47:08 fenrir bluetoothd[40741]: 
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 01 00:47:08 fenrir systemd-logind[1545]: Watching system buttons on 
/dev/input/event19 (Bose QuietComfort 35 (AVRCP))
  Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
  Mar 01 00:47:09 fenrir bluetoothd[40741]: 
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 01 

[Touch-packages] [Bug 1903516] Re: aborted (core dumped) when using ConnectTimeout > 2147483

2022-03-02 Thread Lena Voytek
** Changed in: openssh (Ubuntu Bionic)
   Importance: Undecided => Low

** Changed in: openssh (Ubuntu Focal)
   Importance: Undecided => Low

** Changed in: openssh (Ubuntu Impish)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1903516

Title:
  aborted (core dumped) when using ConnectTimeout > 2147483

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Bionic:
  Triaged
Status in openssh source package in Focal:
  Triaged
Status in openssh source package in Impish:
  Triaged
Status in openssh source package in Jammy:
  Fix Released

Bug description:
  The ssh client fails with the message "Aborted (core dumped)" when
  setting the ConnectTimeout to 2147484 or higher.

  lsb_release: Linux Mint 20 (but also tested this on latest ubuntu:20.04 
docker container)
  openssh-client version: 1:8.2p1-4ubuntu0.1

  I expected that either the connect timeout would be used correctly, or
  that it would fail with a proper error message saying the connect
  timeout can't be higher than 2147483.

  What happened:

  $ ssh -o "ConnectTimeout=2147484" localhost
  Aborted (core dumped)

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssh/+bug/1903516/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1962135] Re: Upgrade defalult gstreamer version 1.16 minor version on ubuntu-20.04

2022-03-02 Thread Jeremy Bicha
** Changed in: gst-plugins-bad1.0 (Ubuntu Focal)
   Status: New => In Progress

** Changed in: gst-plugins-base1.0 (Ubuntu Focal)
   Status: New => In Progress

** Changed in: gstreamer1.0 (Ubuntu Focal)
   Status: New => In Progress

** Changed in: gst-plugins-good1.0 (Ubuntu Focal)
   Status: New => Triaged

** Summary changed:

- Upgrade defalult gstreamer version 1.16 minor version on ubuntu-20.04
+ [SRU] gstreamer 1.16.3

** Summary changed:

- [SRU] gstreamer 1.16.3
+ [SRU] gstreamer 1.16.3 series

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-base1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/1962135

Title:
  [SRU] gstreamer 1.16.3 series

Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 source package in Focal:
  In Progress
Status in gst-plugins-base1.0 source package in Focal:
  In Progress
Status in gst-plugins-good1.0 source package in Focal:
  Triaged
Status in gstreamer1.0 source package in Focal:
  In Progress

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.16 series
  that 20.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  If one of the fixes is bad then it might break video or audio
  playback, or could crash any application that tries to use gstreamer.

  ---


  On ubuntu-20.04 "apt-get" default installs gstreamer version 1.16.2,
  though gstreamer has subsequent minor version gst-1.16.3 with fixes
  incorporated.

  Hence, Ideally default gstreamer-1.16 minor version support with
  ubuntu-20.04 should be upgraded to use gstreamer version 1.16.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1962135/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1962542] Re: [jammy] Bluetooth headphones unable to connect after suspend in BlueZ 5.63

2022-03-02 Thread Daniel van Vugt
** Summary changed:

- Bluetooth headphones unable to connect after suspend
+ [jammy] Bluetooth headphones unable to connect after suspend in BlueZ 5.63

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1962542

Title:
  [jammy] Bluetooth headphones unable to connect after suspend in BlueZ
  5.63

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  Bose quietcomfort 35 is a common headset that can no longer connect to
  a jammy system after just one suspend. This started at the end of
  January but just now really debugging the issue.

  Side note that my bluetooth mouse works fine without problem after any
  amount of suspends.

  The headset is only trying to connect to the jammy system (no other
  bluetooth devices it's paired with has active bluetooth, to isolate
  only the jammy <-> headset issue). This is jammy running on a T590, up
  to date, not proposed.

  heather@fenrir:~$ dpkg -l | grep bluetooth
  ii  gir1.2-gnomebluetooth-1.0:amd643.34.5-4   
amd64Introspection data for GnomeBluetooth
  ii  gnome-bluetooth3.34.5-4   
amd64GNOME Bluetooth tools
  ii  libbluetooth-dev:amd64 5.63-0ubuntu1  
amd64Development files for using the BlueZ Linux Bluetooth 
library
  ii  libbluetooth3:amd645.63-0ubuntu1  
amd64Library to use the BlueZ Linux Bluetooth stack
  ii  libgnome-bluetooth13:amd64 3.34.5-4   
amd64GNOME Bluetooth tools - support library
  ii  pulseaudio-module-bluetooth1:15.99.1+dfsg1-1ubuntu1   
amd64Bluetooth module for PulseAudio sound server

  On a fresh boot (not suspended yet), I can connect the headset
  successfully. Here are the logs of that:

  Mar 01 09:44:02 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as 
/devices/virtual/input/input30
  Mar 01 09:44:02 fenrir systemd-logind[1570]: Watching system buttons on 
/dev/input/event22 (Bose QuietComfort 35 (AVRCP))
  Mar 01 09:44:03 fenrir NetworkManager[1536]:   [1646124243.8660] 
platform-linux: do-add-ip6-address[3: fe80::c1bc:a705:9e66:e0d0]: failure 13 
(Permission denied)
  Mar 01 09:44:04 fenrir bluetoothd[1532]: 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0: fd(32) ready
  Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 6 threads of 3 
processes of 1 users.
  Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Successfully made thread 5660 of 
process 2708 owned by '1000' RT at priority 5.
  Mar 01 09:44:04 fenrir rtkit-daemon[2349]: Supervising 7 threads of 3 
processes of 1 users.
  Mar 01 09:44:04 fenrir pulseaudio[2708]: org.freedesktop.DBus.Properties.Get 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F/fd0 Volume failed: 
org.freedesktop.DBus.Error.InvalidArgs: No such property 'Volume'
  Mar 01 09:44:04 fenrir pulseaudio[2708]: Battery Level: 70%
  Mar 01 09:44:04 fenrir pulseaudio[2708]: Dock Status: undocked

  But then if I close the laptop lid and reopen, login, and try to
  connect the headset the device is found invalid with the following
  logs:

  Mar 01 00:47:08 fenrir kernel: input: Bose QuietComfort 35 (AVRCP) as 
/devices/virtual/input/input152
  Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
  Mar 01 00:47:08 fenrir bluetoothd[40741]: 
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 01 00:47:08 fenrir pulseaudio[253956]: Information about device 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
  Mar 01 00:47:08 fenrir bluetoothd[40741]: 
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 01 00:47:08 fenrir systemd-logind[1545]: Watching system buttons on 
/dev/input/event19 (Bose QuietComfort 35 (AVRCP))
  Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
  Mar 01 00:47:09 fenrir bluetoothd[40741]: 
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 01 00:47:09 fenrir pulseaudio[253956]: Information about device 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F is invalid
  Mar 01 00:47:09 fenrir bluetoothd[40741]: 
profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 01 00:47:09 fenrir pulseaudio[253956]: Device doesn't exist for 
/org/bluez/hci0/dev_60_AB_D2_07_DB_9F
  Mar 01 00:47:09 fenrir bluetoothd[40741]: src/profile.c:new_conn_reply() 
Hands-Free Voice gateway replied with an error: 
org.bluez.Error.InvalidArguments, Unable to handle new connection
  Mar 01