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 do
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 t
# 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 connect_d
This bug is clone from #1217774.
--
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 work after S3/S4 or after turning bluetooth on/off
several times by tog
The workaround:
Put below code to /etc/init/bluetooth.conf, it make bluetoothd wait 0.5 seconds
to startup.
pre-start script
sleep 0.5
end script
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.l
Public bug reported:
After S3/S4 or turning bluetooth on/off several times by toggle key,
there are many error messages in dmesg. And sometime the bluetooth menu is
incomplete.
dmesg:
[ 1117.356421] init: bluetooth main process (3848) terminated with status 1
[ 1117.356506] init: bluetooth main p
6 matches
Mail list logo