Comment # 49 on bug 898395 from Bit Juggler

(In reply to Al Cho from comment #46)
> (In reply to Al Cho from comment #44)
> > (In reply to Bit Juggler from comment #42)
> > > Thank you for your help.
> > > 
> > > Here is what i have done:
> > > 
> > > 1. Started system
> > >    openSUSE 13.2 (Harlequin) (x86_64)
> > >    Linux 3.17.2-3.gbf63174-default
> > >    KDE 4.14.2
> > > 
> > > 2. Logged in as user, started terminal session and became "root"
> > >    # journalctl>01_after_boot.txt
> > >    (see attached file outputs_journalctl.zip)
> > > 
> > > 3. Plugged in USB2.0 bluetooth device (0400:080a)
> > >    # journalctl>01_after_device_plugin.txt
> > >   (see attached file outputs_journalctl.zip)
> > > 
> > > 4. # killall bluetoothd
> > > 
> > > 5. # /usr/lib/bluetooth/bluetoothd -d &
> > > 
> > > 6. # journalctl>01_after_bt_start.txt
> > >   (see attached file outputs_journalctl.zip)
> > > 
> > > Please tell me, if i can provide any more information or testing.
> > 
> > Thanks a lot !
> > 
> > Would you please also do:
> > 
> > #hciconfig hci0 up 
> > (and hciconfig hci0 down )
> > 
> > after your step 5 ?
> > 
> > I am confused hci interface was enabled or not.
> 
> Sorry for my comment#44 is not clearly,
> Would you please do:
> 
> #hciconfig hci0 up 
> (and hciconfig hci0 down )
> after your step 5 ?
> 
> and attach the latest journalctl log file again ?
> I would like to check bluetooth daemon status at that moment.


None of the "hciconfig"-commands described in comment#45 produced any
additional messages in the journal. I already mentioned this in comment#45. 

I proofed this by doing 

# journalctl>xx_log.txt

before the first and after every "hciconfig"-command issued and comparing the
resulting xx_log.txt files with the KDE tool "Kompare". All the files were
identical.