kernel-packages team mailing list archive

[Ralf Hildebrandt <Ralf.Hildebrandt@xxxxxxxxxx>]

Added hci.log as per debugging instructions.

* mouse was working
* I started the generation of the hci.log
* I supended
* I resumed
* Mouse was not working
* I performed my "workaround" (during which the generation of the log ended)


** Attachment added: "hci.log as per debugging instructions."
   https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1229307/+attachment/3836789/+files/hci.log

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

Title:
  paired device doesn't reconnect after suspend

Status in “bluez” package in Ubuntu:
  New

Bug description:
  I use a bluetooth mouse. After I suspend/resume the system, I have
  issues using it.

  One workaround I found is to go into the bluetooth menu, select the
  menu "Microsoft bluetooth mouse 5000", and click on the (already
  ticked!) "Connection" submenu.

  This causes the bluetooth menu to disappear entirely and reappear
  after an instant. THEN the mouse is actually connected and usable.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluez 4.101-0ubuntu8b1
  ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
  Uname: Linux 3.11.0-7-generic x86_64
  ApportVersion: 2.12.4-0ubuntu1
  Architecture: amd64
  Date: Mon Sep 23 19:10:12 2013
  InstallationDate: Installed on 2013-02-14 (220 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  InterestingModules: btusb rfcomm bnep bluetooth
  MachineType: FUJITSU SIEMENS LIFEBOOK P8010
  MarkForUpload: True
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-7-generic root=UUID=a7c2748a-3784-49ab-aac1-ee1f5b62b769 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to saucy on 2013-09-08 (15 days ago)
  dmi.bios.date: 08/20/2008
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.08
  dmi.board.name: FJNB1E3
  dmi.board.vendor: FUJITSU
  dmi.board.version: CP365186-01
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU SIEMENS
  dmi.chassis.version: P8010
  dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.08:bd08/20/2008:svnFUJITSUSIEMENS:pnLIFEBOOKP8010:pvr:rvnFUJITSU:rnFJNB1E3:rvrCP365186-01:cvnFUJITSUSIEMENS:ct10:cvrP8010:
  dmi.product.name: LIFEBOOK P8010
  dmi.sys.vendor: FUJITSU SIEMENS
  hciconfig:
   hci0:	Type: BR/EDR  Bus: USB
   	BD Address: 00:03:7A:76:AE:F9  ACL MTU: 310:10  SCO MTU: 64:8
   	UP RUNNING PSCAN 
   	RX bytes:10084 acl:618 sco:0 events:57 errors:0
   	TX bytes:570 acl:12 sco:0 commands:23 errors:0

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