The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: linux (Ubuntu Precise)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
keep watching on this bug but not to reopen it, because:
1, we actually have no public release with that version module.
2, it's fixed in kernel 3.14 as #11.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
** Changed in: bluez (Ubuntu)
Status: Incomplete = Invalid
** Changed in: bluez (Ubuntu Precise)
Status: Incomplete = Invalid
** Changed in: oem-priority
Status: Confirmed = Invalid
** Changed in: oem-priority/precise
Status: Confirmed = Invalid
--
You received
Marking as Invalid in Bluez and oem-priority, based on latest comments
(that suggests the problem is in the driver)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1221618
Title:
On Wed, Feb 12, 2014 at 06:42:13AM -, Bruce.Ma wrote:
Test this with the latest daily of trusty 3.14.0-031400rc2-generic on
T540-1(Kome-T-1), didn't see this issue.
In that case you should be able to use the mainline builds to find
roughly where the fix was introduced and then use git
Test this with the latest daily of trusty 3.14.0-031400rc2-generic on
T540-1(Kome-T-1), didn't see this issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1221618
Title:
Bluetooth
This log file is at:
https://bugs.launchpad.net/sutton/+bug/1217774/+attachment/3791364/+files/T540-2013-08-28-logs.tgz
** Attachment added: T540-2013-08-28-logs.tgz
https://bugs.launchpad.net/oem-priority/+bug/1221618/+attachment/3949941/+files/T540-2013-08-28-logs.tgz
--
You received
A few observations.
The kernel messages pointed out here aren't come from anything in the
precise kernel but rather from modules included via compat-drivers. I
found that compat-wireless-3.10-dkms 3.10~rc1~2.20130618.sutton3 is
installed, and if that's really coming from an rc1 kernel then there
There is absolutely no reason why delaying bluez from starting should
affect S3/S4 or killswitches in any normal case, especially not in a
relation with dbus, for which the connection is only established on
startup.
There *is* a chance where bluetooth would start and not have dbus
available, but
Found a dmesg output from the other bug; I think this is likely a strong
hint towards the actual problem:
[ 6135.609315] Bluetooth: hci0 reading Intel fw version command failed (-110)
[ 6137.610607] Bluetooth: hci0 command 0x0c03 tx timeout
[ 6145.595944] Bluetooth: hci0 sending initial HCI reset
This seems a lot like a user space race. bluez is trying to do stuff
with the driver before the firmware is loaded. Is there a way to
construct the udev rule such that bluez doesn't get started until after
the firmware load is done ?
--
You received this bug notification because you are a member
By the looks of things this is a platform wherein the actual bluetooth
controller is powered off when the kill switch is turned on, and powered
up again when the switch is turned off. Thus the controller is
initialising when the event is emitted, which starts the bluez which is
getting there
** Changed in: oem-priority/precise
Status: New = Confirmed
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) = Canonical Desktop Team (canonical-desktop-team)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in
** Changed in: bluez (Ubuntu Precise)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1221618
Title:
Bluetooth doesn't
** Also affects: bluez (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: oem-priority
Status: New = Confirmed
** Changed in: oem-priority
Importance: Undecided = High
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Also affects: bluez
Importance: Undecided
Status: New
** Also affects: oem-priority
Importance: Undecided
Status: New
** Also affects: oem-priority/precise
Importance: Undecided
Status: New
** Changed in: oem-priority
Assignee: (unassigned) = Ara Pulido
# Root cause, if the bluetooth(kernel module and hardware) didn't finished the
initial. Then:
bluez-4.98/src/main.c :
439 int main(int argc, char *argv[])
... ..
511 if (connect_dbus() 0) {
512 error(Unable to get on D-Bus);
// The function
17 matches
Mail list logo
