Going to wontfix for bionic since there doesn't seem to be a need for it
at this point
** Changed in: bluez (Ubuntu Bionic)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in
** Changed in: oem-priority
Status: In Progress => 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/1887910
Title:
[bionic]blutoothd segfault when you
Unsubscribing sponsors for now, Alex are you still working on that?
Please subscribe the team back if you get something ready for upload
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
It's seems not just one patch can fix this issue. I found another corner
case that still can trigger a blutoothd segmentation fault.
I pair one Bluetooth keyboard but cancel before input pairing keycode.
Before timeout of latest keyboard pairing, I pair another Bluetooth
keyboard and still cancel
** Changed in: bluez (Ubuntu Bionic)
Status: In Progress => Confirmed
--
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/1887910
Title:
[bionic]blutoothd segfault when
sorry for bad habit that I miss-understanded before.
I revised it and put detail information there.
--
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/1887910
Title:
** Description changed:
[Impact]
- * only impact Bionic machines because series after Bionic already
- included this patch.
+ This patch is for this issue:
+ steps:
+ 1. pair bluetooth keyboard
+ 2. see the dialog asking user input the code for pairing.
+ 3. press "esc" to cancel it.
+
Alex, did you read comment 7? 'low' isn't responding to what the
regression potential should provide, it's there to describe what impact
the change could have to know on what to focus the testing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Sorry,
the debugging and debdiff was done on the target machine so that the email ID
was missed.
This attached new debdiff also included the patch and lp number
information in the changelog.
And also updated the truncated description.
** Patch added: "bluez_5.48-0ubuntu3.5.debdiff"
** Description changed:
[Impact]
- * only impact Bionic machines because series after Bionic already
+ * only impact Bionic machines because series after Bionic already
included this patch.
[Test Case]
- 1. pair bluetooth keyboard
- 2. see the dialog asking user input the code
Oh, I can't remove Ubuntu Sponsors. Still, please fix all of the above.
** Also affects: bluez (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: bluez (Ubuntu Groovy)
Importance: High
Status: In Progress
** Also affects: bluez (Ubuntu Bionic)
Importance:
BTW the fix first appeared in 5.50 (commit
f1b8cdef95d6b51cab122f2be0694521f47092d0).
--
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/1887910
Title:
[bionic]blutoothd
I'm going to remove Ubuntu Sponsors from this briefly, until the
following are fixed:
1. The issue mentioned in comment #7 - The Bug Description on this page
needs improving.
2. The email address used in the patch needs replacing
with your real email.
3. Need to mention the bug ID and the
** Changed in: bluez (Ubuntu)
Status: Incomplete => In Progress
--
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/1887910
Title:
[bionic]blutoothd segfault when you
@Alex, sorry I though you were familiar with the SRU process, see
https://wiki.ubuntu.com/StableReleaseUpdates for details
especially
'A [Regression Potential] section with a discussion of how regressions
are most likely to manifest, or may manifest even if it is unlikely, as
a result of this
@seb128, yes, I modified the description and the debdiff is there in #4.
** Description changed:
- steps:
+ [Impact]
+
+ * only impact Bionic machines because series after Bionic already
+ included this patch.
+
+ [Test Case]
+
1. pair bluetooth keyboard
2. see the dialog asking user
@Alex, thanks, a few comments:
* could you make the bug SRU compliant (adding a description of the
impact and the regression potential)
* it would be nice to have an user friendly description of what the
patch is solving in the changelog, also the email you used is not a
valid one
* could you
this is the debdiff which applied the patch , and I also host the
modified code there :
https://code.launchpad.net/~alextu/ubuntu/+source/bluez/+git/bluez/+ref/lp1887910
-bluetoothd-segv-keyboard
** Patch added: "bluez_5.48-0ubuntu3.5.debdiff"
It's good you know the fix already. Otherwise you might need this workaround to
get a core dump:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1870060/comments/3
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez
Is the issue fixed in the current version? Do you plan to work on a SRU
and targetting what serie?
** Changed in: bluez (Ubuntu)
Importance: Undecided => High
** Changed in: bluez (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
after this patch, the issue can not be reproduced:
commit 24249e091ab3a935f6ea87b7f7355c689c045a80 (HEAD -> refs/heads/master)
Author: Luiz Augusto von Dentz
Date: Mon Apr 9 14:48:41 2018 +0300
shared/queue: Handle NULL as direct match on queue_remove_if
As with queue_find when
21 matches
Mail list logo
