Computer not stated if bluetoot adapter is a connected.

[Tuomas Lähteenmäki]

Binary package hint: bluez

if im starting computer and Trust bluetooth adapter and adapter is a connected usb 2.0 card.
Ubuntu lucid not started. Crashed in black screen and not started.

If im a remove bluetooth adapter and started computer again. Computer started a fast.
Then im a plugin a bluetooth adapter usb-card and bluetooth found and operate a normal.
File transfer work out a normal.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: bluez 4.60-0ubuntu8
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Thu May 27 21:35:29 2010
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
InterestingModules: rfcomm sco bnep l2cap btusb bluetooth
MachineType: MSI MS-6380
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=a46cf04f-a734-4133-a9b8-3604c7c5b0fd ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
SourcePackage: bluez
dmi.bios.date: 01/31/2002
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 07.00T
dmi.board.name: MS-6380
dmi.board.vendor: MSI
dmi.board.version: 2.0
dmi.chassis.asset.tag: 0123ABC
dmi.chassis.type: 3
dmi.chassis.vendor: Uknown Chassis Manufacture
dmi.chassis.version: Version 1.00
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr07.00T:bd01/31/2002:svnMSI:pnMS-6380:pvr2.0:rvnMSI:rnMS-6380:rvr2.0:cvnUknownChassisManufacture:ct3:cvrVersion1.00:
dmi.product.name: MS-6380
dmi.product.version: 2.0
dmi.sys.vendor: MSI
hciconfig:
 hci0: Type: USB
  BD Address: 00:02:72:A4:5F:49 ACL MTU: 1021:7 SCO MTU: 64:1
  UP RUNNING PSCAN
  RX bytes:13131 acl:73 sco:0 events:79 errors:0
  TX bytes:2023 acl:26 sco:0 commands:42 errors:0
rfkill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Mörgæs (moergaes)]

Closing due to age.
If a similar bug appears in 13.10 please open a new report.