ubuntu at mfraz.orangehome.co.uk
Mon Feb 8 14:26:41 GMT 2010
On Monday 08 Feb 2010 05:30:05 Howard Coles Jr. wrote:
> On Sunday 07 February 2010 05:38:37 pm Eric wrote:
> > Howard Coles wrote:
> > > First check to make sure its installed, then look in "/etc/unit.d" for
> > > the bluez start/stop script. If its there try to restart it by running
> > > "./bluez restart" (or whatever the blue* script is called).
> > I used mlocate to search and I got a ton of information, I couldn't find
> > /etc/unit.d
> > Here is the result of mlocate. Can you see if bluez is installed please?
> > ericjackson at ericjackson-laptop:~$ mlocate bluez
> That's what I get for trying to use my Android to answer.
> its "/etc/init.d" not unit.d sorry.
> And, since I'm now on my Kubuntu box, I found the stop and restart file:
> /etc/init.d/bluetooth restart
> You should see something like the following after running: ps -ef | grep
> root 1674 1 0 07:21 ? 00:00:00 /usr/sbin/bluetoothd --udev
> userid 2134 1 0 07:23 ? 00:00:00 kbluetooth -session <bunch
> of long numbers>
> userid 2168 2040 0 07:23 ? 00:00:00 /usr/bin/python
I'm also having trouble trying to get bluetooth working on one computer, in
that KBluetooth appears in the system tray, but if I try to change the adapter
name or mode it will change for that session, but if I reboot it goes back to
the original settings.
Doing ps -ef | grep gives:
root 29 2 0 07:27 ? 00:00:00 [bluetooth]
root 2197 1 0 07:27 ? 00:00:00 /usr/sbin/bluetoothd --udev
tfraser 2631 1 0 07:27 ? 00:00:00 kbluetooth -session
tfraser 2657 2543 0 07:28 ? 00:00:00 /usr/bin/python /usr/bin/kblueplugd
mfraser 4006 3972 0 14:21 pts/1 00:00:00 grep blue
Registered Linux User #466407 http://counter.li.org
More information about the kubuntu-users