Page 4 of 4
Posted: Wed 02 Jan 2013, 22:29
by chursch
I tried running Master_wrong's list of commands in an LXTerminal. Basically, my first attempt on the command line with copy-and-paste into the terminal had me in bash, so I started a sub-sh so I had the correct shell type. Then copy-and-pasted into that. The main issue then was that it appears that hciconfig was in in /usr/sbin rather than /usr/local/sbin. So eventually got through it all with what appears to be success, except that there appears to be no blueman-applet. I scanned the entire system for blueman-applet, and it doesn't exist anywhere. Soooo...
Also, I didn't have a bluetooth dongle in the USB port for my first couple of attempts, but by the last attempt it had occurred to me that might make a difference, so I plugged one in. Anyways, no blueman-applet and no bluetooth-looking icon anywhere on the screen. The readout is in the box.
In LXTerminal:
# #!/bin/sh
#
# dbus-uuidgen --ensure &
[1] 7433
#
# dbus-daemon --system
Failed to start message bus: The pid file "/var/run/dbus/dbus.pid" exists, if the message bus is not running, remove this file
[1]+ Done dbus-uuidgen --ensure
#
# modprobe bluetooth
#
# modprobe l2cap
#
# modprobe rfcomm
#
# modprobe btusb
#
# /usr/local/sbin/hciconfig hci0 up
bash: /usr/local/sbin/hciconfig: No such file or directory
#
# /usr/local/sbin/hciconfig hci0 class 0x3e0100
bash: /usr/local/sbin/hciconfig: No such file or directory
#
# mknod -m 666 /dev/rfcomm0 c 216 0
#
# bluetoothd
#
# mkdir /root/a
#
# hcitool scan
Device is not available: No such device
#
# blueman-applet
bash: blueman-applet: command not found
#
I also tried in /bin/sh in terminal:
Results (hciconfig is in /usr/sbin rather than /usr/local/sbin so retyped those commands - still no blueman-applet, and find didn't find blueman-applet on the system; bluetooth dongle in the usb port):
# dbus-uuidgen --ensure &
[1] 28567
#
# dbus-daemon --system
Failed to start message bus: The pid file "/var/run/dbus/dbus.pid" exists, if the message bus is not running, remove this file
[1]+ Done dbus-uuidgen --ensure
#
# modprobe bluetooth
#
# modprobe l2cap
#
# modprobe rfcomm
#
# modprobe btusb
#
# /usr/local/sbin/hciconfig hci0 up
sh: /usr/local/sbin/hciconfig: No such file or directory
#
# /usr/local/sbin/hciconfig hci0 class 0x3e0100
sh: /usr/local/sbin/hciconfig: No such file or directory
#
# mknod -m 666 /dev/rfcomm0 c 216 0
mknod: /dev/rfcomm0: File exists
#
# bluetoothd
#
# mkdir /root/a
mkdir: cannot create directory '/root/a': File exists
#
# hcitool scan
Scanning ...
#
# blueman-applet
sh: blueman-applet: command not found
# /usr/sbin/hciconfig hci0 up
# /usr/sbin/hciconfig hci0 class 0x3e0100
# mknod -m 666 /dev/rfcomm0 c 216 0
mknod: /dev/rfcomm0: File exists
# bluetoothd
# hcitool scan
Scanning ...
# blueman-applet
sh: blueman-applet: command not found
#
Posted: Thu 03 Jan 2013, 18:04
by capicoso
chursch wrote:I tried running Master_wrong's list of commands in an LXTerminal. Basically, my first attempt on the command line with copy-and-paste into the terminal had me in bash, so I started a sub-sh so I had the correct shell type. Then copy-and-pasted into that. The main issue then was that it appears that hciconfig was in in /usr/sbin rather than /usr/local/sbin. So eventually got through it all with what appears to be success, except that there appears to be no blueman-applet. I scanned the entire system for blueman-applet, and it doesn't exist anywhere. Soooo...
Also, I didn't have a bluetooth dongle in the USB port for my first couple of attempts, but by the last attempt it had occurred to me that might make a difference, so I plugged one in. Anyways, no blueman-applet and no bluetooth-looking icon anywhere on the screen. The readout is in the box.
In LXTerminal:
# #!/bin/sh
#
# dbus-uuidgen --ensure &
[1] 7433
#
# dbus-daemon --system
Failed to start message bus: The pid file "/var/run/dbus/dbus.pid" exists, if the message bus is not running, remove this file
[1]+ Done dbus-uuidgen --ensure
#
# modprobe bluetooth
#
# modprobe l2cap
#
# modprobe rfcomm
#
# modprobe btusb
#
# /usr/local/sbin/hciconfig hci0 up
bash: /usr/local/sbin/hciconfig: No such file or directory
#
# /usr/local/sbin/hciconfig hci0 class 0x3e0100
bash: /usr/local/sbin/hciconfig: No such file or directory
#
# mknod -m 666 /dev/rfcomm0 c 216 0
#
# bluetoothd
#
# mkdir /root/a
#
# hcitool scan
Device is not available: No such device
#
# blueman-applet
bash: blueman-applet: command not found
#
I also tried in /bin/sh in terminal:
Results (hciconfig is in /usr/sbin rather than /usr/local/sbin so retyped those commands - still no blueman-applet, and find didn't find blueman-applet on the system; bluetooth dongle in the usb port):
# dbus-uuidgen --ensure &
[1] 28567
#
# dbus-daemon --system
Failed to start message bus: The pid file "/var/run/dbus/dbus.pid" exists, if the message bus is not running, remove this file
[1]+ Done dbus-uuidgen --ensure
#
# modprobe bluetooth
#
# modprobe l2cap
#
# modprobe rfcomm
#
# modprobe btusb
#
# /usr/local/sbin/hciconfig hci0 up
sh: /usr/local/sbin/hciconfig: No such file or directory
#
# /usr/local/sbin/hciconfig hci0 class 0x3e0100
sh: /usr/local/sbin/hciconfig: No such file or directory
#
# mknod -m 666 /dev/rfcomm0 c 216 0
mknod: /dev/rfcomm0: File exists
#
# bluetoothd
#
# mkdir /root/a
mkdir: cannot create directory '/root/a': File exists
#
# hcitool scan
Scanning ...
#
# blueman-applet
sh: blueman-applet: command not found
# /usr/sbin/hciconfig hci0 up
# /usr/sbin/hciconfig hci0 class 0x3e0100
# mknod -m 666 /dev/rfcomm0 c 216 0
mknod: /dev/rfcomm0: File exists
# bluetoothd
# hcitool scan
Scanning ...
# blueman-applet
sh: blueman-applet: command not found
#
hello. When i had to do this, instead of typing the whole rute /usr/sbin/hciconfig. I just type hcic then tab to see if it sees the command, and then i get hciconfig. This is how i always do it, the same with hcitool. Also, when i did it i didn't hvae any blueman-applet but blueman-manager. Try and check if you have that command
Posted: Mon 07 Jan 2013, 22:44
by chursch
No blueman-manager, no blueman anything after searching the system with the Ptfind (sic?) utility. What is missing? I added all the pets on the list...
Posted: Thu 10 Jan 2013, 11:15
by Master_wrong
@chursch
I really dont understand why you cant run blueman when the difference is that you are using lxterm and alwaysalone is using roxterm ?
can you try using the roxterm ?
EDIT :
Failed to start message bus: The pid file "/var/run/dbus/dbus.pid" exists, if the message bus is not running, remove this file
you can rename or delete this files and try again
Posted: Sun 13 Jan 2013, 06:03
by chursch
I tried roxterm for the list of command, including blueman-applet/manager. Didn't really expect it to work, and it didn't.
So why don't I have a blueman guy? I'm sure I loaded the pet...