Page 1 of 2
Bluez 4.61 with GUI
Posted: Sun 28 Feb 2010, 03:04
by jemimah
This is an unholy union of bluez-gnome and gnome-bluetooth. The applet from the gnome-bluetooth project wants a newer gtk and a newer kernel than Puppy 4.3.1 has, however the Sendto and Wizard GUIs build ok and work better than the sendto and wizard guis in bluez-gnome. So this is the bluez-gnome applet with the wizard and sendto gui from gnome-bluetooth.
Install all the pets below and reboot. Make sure any old bluez packages are removed.
Posted: Sun 28 Feb 2010, 03:08
by jemimah
And the dev and nls pets are here.
Posted: Sun 28 Feb 2010, 05:21
by pri
testing.......
instaled and bluetoth icon not come out.
trying to post the problem and when open firefox, firefox was crash.
test on cli to find out what wrong....
and this is the result :
# cd Startup/
# ls
bluetooth README.txt start_cpu_freq
# ./bluetooth
+ killall dbus-launch
killall: dbus-launch: no process killed
+ killall bluetoothd
killall: bluetoothd: no process killed
+ killall bluetooth-applet
killall: bluetooth-applet: no process killed
+ killall obexd
killall: obexd: no process killed
+ /etc/init.d/dbus restart
./bluetooth: line 9: /etc/init.d/dbus: No such file or directory
+ sleep 1
+ mkdir /root/bluetooth-share
+ bluetoothd -n
+ /usr/libexec/obexd --ftp --opp -r /root/bluetooth-share -n
+ sleep 1
process 30605: D-Bus library appears to be incorrectly set up; failed to read machine uuid: Failed to open "/var/lib/dbus/machine-id": No such file or directory
See the manual page for dbus-uuidgen to correct this issue.
D-Bus not built with -rdynamic so unable to print a backtrace
bluetoothd[30604]: Bluetooth daemon 4.61
bluetoothd[30604]: Unable to get on D-Bus
./bluetooth: line 14: 30605 Aborted /usr/libexec/obexd --ftp --opp -r /root/bluetooth-share -n
+ bluetooth-applet
# process 30607: D-Bus library appears to be incorrectly set up; failed to read machine uuid: Failed to open "/var/lib/dbus/machine-id": No such file or directory
See the manual page for dbus-uuidgen to correct this issue.
D-Bus not built with -rdynamic so unable to print a backtrace
now i am posting this using opera.
Posted: Sun 28 Feb 2010, 16:24
by jemimah
Run '/etc/init.d/dbus restart' from the command line and see what the error is.
Posted: Sun 28 Feb 2010, 18:07
by pri
cant found that file
Posted: Sun 28 Feb 2010, 18:48
by jemimah
Did you install the dbus pet? Maybe try installing it again.
Posted: Sun 28 Feb 2010, 21:57
by pri
/usr/
/usr/lib/
/usr/lib/libdbus-glib-1.so.2.1.0
/usr/lib/libdbus-glib-1.la
/usr/lib/libdbus-glib-1.a
/usr/lib/pkgconfig/
/usr/lib/pkgconfig/dbus-glib-1.pc
/usr/lib/libdbus-glib-1.so.2
/usr/lib/libdbus-glib-1.so
/usr/bin/
/usr/bin/dbus-binding-tool
/usr/libexec/
/usr/libexec/dbus-bash-completion-helper
/usr/etc/
/usr/etc/bash_completion.d/
/usr/etc/bash_completion.d/dbus-bash-completion.sh
that was dbus, and from the first the problem is from dbus.
i have firefox on my puppy, i mustbe have dbus first instaled.
Posted: Sun 28 Feb 2010, 22:20
by jemimah
Oops, I forgot to post the dbus pet.
I've added it to the first post now.
Posted: Mon 01 Mar 2010, 07:39
by pri
bluetooth icon not show up when start puppy, then i try to click the bluetooth on startup, and not show up too then click again and now show up.
there is must be wrong with your script
this is the result :
# cd Startup/
# ./bluetooth
+ killall dbus-launch
+ killall bluetoothd
+ killall bluetooth-applet
killall: bluetooth-applet: no process killed
+ killall obexd
+ /etc/init.d/dbus restart
Stopping system message bus...
27057 ? Zs 0:00 dbus-daemon <defunct>
+ sleep 1
+ mkdir /root/bluetooth-share
+ bluetoothd -n
+ /usr/libexec/obexd --ftp --opp -r /root/bluetooth-share -n
bluetoothd[27724]: Bluetooth daemon 4.61
bluetoothd[27724]: Unable to get on D-Bus
+ sleep 1
Failed to connect to socket /tmp/dbus-EM0LDowoVu: Connection refused
obexd[27725]: manager_init failed
+ bluetooth-applet
# Can't get session bus: Failed to connect to socket /tmp/dbus-EM0LDowoVu: Connection refused
./bluetooth
+ killall dbus-launch
+ killall bluetoothd
killall: bluetoothd: no process killed
+ killall bluetooth-applet
killall: bluetooth-applet: no process killed
+ killall obexd
killall: obexd: no process killed
+ /etc/init.d/dbus restart
Starting system message bus: /usr/bin/dbus-uuidgen --ensure ; /usr/bin/dbus-daemon --system
+ sleep 1
+ mkdir /root/bluetooth-share
+ bluetoothd -n
+ /usr/libexec/obexd --ftp --opp -r /root/bluetooth-share -n
bluetoothd[32706]: Bluetooth daemon 4.61
bluetoothd[32706]: Starting SDP server
+ sleep 1
bluetoothd[32706]: Parsing /usr/etc/bluetooth/network.conf failed: No such file or directory
bluetoothd[32706]: Can't create GN bridge
bluetoothd[32706]: Parsing /usr/etc/bluetooth/input.conf failed: No such file or directory
bluetoothd[32706]: Parsing /usr/etc/bluetooth/audio.conf failed: No such file or directory
bluetoothd[32706]: HCI dev 0 registered
bluetoothd[32706]: HCI dev 0 up
bluetoothd[32706]: Starting security manager 0
Failed to connect to socket /tmp/dbus-B3J9KHlYUo: Connection refused
obexd[32707]: manager_init failed
bluetoothd[32706]: Parsing /usr/etc/bluetooth/serial.conf failed: No such file or directory
(bluetoothd:32706): GLib-CRITICAL **: g_key_file_get_boolean: assertion `key_file != NULL' failed
bluetoothd[32706]: Adapter /org/bluez/32706/hci0 has been enabled
bluetoothd[32706]: Failed to open RFKILL control device
bluetoothd[32706]: Failed to access HAL
+ bluetooth-applet
# Can't get session bus: Failed to connect to socket /tmp/dbus-B3J9KHlYUo: Connection refused
./bluetooth
+ killall dbus-launch
killall: dbus-launch: no process killed
+ killall bluetoothd
bluetoothd[32706]: Can't remove GN bridge
bluetoothd[32706]: Stopping SDP server
bluetoothd[32706]: Exit
+ killall bluetooth-applet
killall: bluetooth-applet: no process killed
+ killall obexd
killall: obexd: no process killed
+ /etc/init.d/dbus restart
Stopping system message bus...
32703 ? Zs 0:00 dbus-daemon <defunct>
+ sleep 1
+ mkdir /root/bluetooth-share
+ bluetoothd -n
+ /usr/libexec/obexd --ftp --opp -r /root/bluetooth-share -n
bluetoothd[364]: Bluetooth daemon 4.61
bluetoothd[364]: Unable to get on D-Bus
+ sleep 1
obexd[365]: manager_init failed
+ bluetooth-applet
# Connecting to system bus failed: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused
** (bluetooth-applet:372): CRITICAL **: dbus_g_proxy_new_for_name: assertion `connection != NULL' failed
** (bluetooth-applet:372): CRITICAL **: dbus_g_proxy_add_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (bluetooth-applet:372): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (bluetooth-applet:372): CRITICAL **: dbus_g_proxy_new_for_name: assertion `connection != NULL' failed
** (bluetooth-applet:372): CRITICAL **: dbus_g_proxy_add_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (bluetooth-applet:372): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (bluetooth-applet:372): CRITICAL **: dbus_g_proxy_add_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (bluetooth-applet:372): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (bluetooth-applet:372): CRITICAL **: dbus_g_proxy_add_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (bluetooth-applet:372): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (bluetooth-applet:372): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (bluetooth-applet:372): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
./bluetooth
+ killall dbus-launch
+ killall bluetoothd
killall: bluetoothd: no process killed
+ killall bluetooth-applet
killall: bluetooth-applet: no process killed
+ killall obexd
killall: obexd: no process killed
+ /etc/init.d/dbus restart
370 ? Zs 0:00 dbus-daemon <defunct>
+ sleep 1
+ mkdir /root/bluetooth-share
+ bluetoothd -n
+ /usr/libexec/obexd --ftp --opp -r /root/bluetooth-share -n
bluetoothd[437]: Bluetooth daemon 4.61
bluetoothd[437]: Unable to get on D-Bus
+ sleep 1
Failed to connect to socket /tmp/dbus-m1HbI48oYo: Connection refused
obexd[438]: manager_init failed
+ bluetooth-applet
# Can't get session bus: Failed to connect to socket /tmp/dbus-m1HbI48oYo: Connection refused
./bluetooth
+ killall dbus-launch
killall: dbus-launch: no process killed
+ killall bluetoothd
killall: bluetoothd: no process killed
+ killall bluetooth-applet
killall: bluetooth-applet: no process killed
+ killall obexd
killall: obexd: no process killed
+ /etc/init.d/dbus restart
Starting system message bus: /usr/bin/dbus-uuidgen --ensure ; /usr/bin/dbus-daemon --system
+ sleep 1
+ mkdir /root/bluetooth-share
+ bluetoothd -n
+ /usr/libexec/obexd --ftp --opp -r /root/bluetooth-share -n
bluetoothd[508]: Bluetooth daemon 4.61
bluetoothd[508]: Starting SDP server
+ sleep 1
bluetoothd[508]: Parsing /usr/etc/bluetooth/network.conf failed: No such file or directory
bluetoothd[508]: Can't create GN bridge
bluetoothd[508]: Parsing /usr/etc/bluetooth/input.conf failed: No such file or directory
bluetoothd[508]: Parsing /usr/etc/bluetooth/audio.conf failed: No such file or directory
bluetoothd[508]: HCI dev 0 registered
bluetoothd[508]: HCI dev 0 up
bluetoothd[508]: Starting security manager 0
bluetoothd[508]: Parsing /usr/etc/bluetooth/serial.conf failed: No such file or directory
(bluetoothd:508): GLib-CRITICAL **: g_key_file_get_boolean: assertion `key_file != NULL' failed
bluetoothd[508]: Adapter /org/bluez/508/hci0 has been enabled
bluetoothd[508]: Failed to open RFKILL control device
bluetoothd[508]: Failed to access HAL
+ bluetooth-applet
#
its about 3 time, then bluetooth show up and not working.
Posted: Mon 01 Mar 2010, 17:32
by jemimah
Dbus is crashing. Can you try in on a clean install of 4.3.1? I'm not sure if your firefox install included dbus files that might mess it up, or what.
Posted: Thu 04 Mar 2010, 13:03
by Pro
Hello,
obex-data-server size 0 byte It is correct?
obexd as always does not work in my system
Why so many dependences became at bluez-gnome? Earlier all worked without it....
icon in system tray not visible
Posted: Sat 06 Mar 2010, 12:50
by aarf
Posted: Sun 07 Mar 2010, 06:02
by aarf
clean new 431 pupsave:
Code: Select all
# ./bluetooth
+ killall dbus-launch
killall: dbus-launch: no process killed
+ killall bluetoothd
killall: bluetoothd: no process killed
+ killall bluetooth-applet
killall: bluetooth-applet: no process killed
+ killall obexd
killall: obexd: no process killed
+ /etc/init.d/dbus restart
Starting system message bus: /usr/bin/dbus-uuidgen --ensure ; /usr/bin/dbus-dae mon --system
Could not create file /var/lib/dbus/machine-id: No such file or directory
Failed to start message bus: Failed to bind socket "/var/run/dbus/system_bus_soc
ket": No such file or directory
+ sleep 1
+ mkdir /root/bluetooth-share
+ bluetoothd -n
bluetoothd[7716]: Bluetooth daemon 4.61
bluetoothd[7716]: Unable to get on D-Bus
+ /usr/libexec/obexd --ftp --opp -r /root/bluetooth-share -n
+ sleep 1
process 7717: D-Bus library appears to be incorrectly set up; failed to read mac hine uuid: Failed to open "/var/lib/dbus/machine-id": No such file or directory
See the manual page for dbus-uuidgen to correct this issue.
D-Bus not built with -rdynamic so unable to print a backtrace
./bluetooth: line 14: 7717 Aborted /usr/libexec/obexd --ftp --o pp -r /root/bluetooth-share -n
+ bluetooth-applet
# process 7719: D-Bus library appears to be incorrectly set up; failed to read m achine uuid: Failed to open "/var/lib/dbus/machine-id": No such file or director y
See the manual page for dbus-uuidgen to correct this issue.
D-Bus not built with -rdynamic so unable to print a backtrace
# /etc/init.d/dbus restart
Starting system message bus: /usr/bin/dbus-uuidgen --ensure ; /usr/bin/dbus-dae mon --system
Could not create file /var/lib/dbus/machine-id: No such file or directory
Failed to start message bus: Failed to bind socket "/var/run/dbus/system_bus_soc ket": No such file or directory
#
Posted: Wed 10 Mar 2010, 13:17
by Pro
Code: Select all
Could not create file /var/lib/dbus/machine-id: No such file or directory
Hi, please verify /var/lib/dbus directory is exist? if no - make it
Posted: Wed 10 Mar 2010, 14:06
by ttuuxxx
Pro wrote:Code: Select all
Could not create file /var/lib/dbus/machine-id: No such file or directory
Hi, please verify /var/lib/dbus directory is exist? if no - make it
To make your dbus ID, First make a folder in /var/lib/dbus and then I usually open as text /root/.xinitrc
go to the very bottom of the script and from there go up a couple lines and add whats highlited in blue below. then restartX server and you should be good to go.
dbus-uuidgen --ensure &
#exec $CURRENTWM
#v2.11 GuestToo suggested this improvement...
which $CURRENTWM >/dev/null && exec $CURRENTWM
[ -x $CURRENTWM ] && exec $CURRENTWM
exec jwm
ttuuxxx
Posted: Wed 10 Mar 2010, 15:13
by jemimah
I did have some test runs where the installer would not create the /var/run/dbus and /var/lib/dbus directories. They are in the pet, but I guess it's a bug in the installer.
When I get a chance, I'll see if I can update the dbus pet to be more forceful about this.
Posted: Wed 10 Mar 2010, 16:45
by ttuuxxx
all you have to is have a blank /var/lib/dbus/ directory
and have the user add
dbus-uuidgen --ensure &
to near the bottom of his/her /root/.xinitrc file:)
ttuuxxx
Posted: Wed 10 Mar 2010, 17:49
by jemimah
It's already in the /etc/init.d/dbus script. Creating the directories that are missing should be good enough to get it going.
Posted: Fri 12 Mar 2010, 14:27
by aarf
created blank directory /var/lib/dbus/
and did the modification
but still got errors and no gui until after adding the second directory at /var/run/dbus
however still not connected.
puppy sees mobile phone Sony-erricsonG502 but phone doesn't see puppy.
phone is using same settings that enable bluetooth connection in knoppix531 immediately before booting puppy431.
g502 connects via USB cable using pupdial and has modem detected as ttyACM0
gprs-connect detects ttyS0 but fails to connect.
sending via bluetooth stops at the image screen below and doesn't send and doesn't show as connected on the phone.
various code cut at various times most interesting is perhaps
bluetooth-wizar[12453]: segfault at 0 ip b7e5e980 sp bf908e60 error 4 in libdbus -1.so.3.4.0[b7e54000+35000]
see below for context
Code: Select all
ath5k 0000:01:00.0: registered as 'phy0'
i801_smbus 0000:00:1f.3: PCI INT B -> Link[LNKD] -> GSI 7 (level, low) -> IRQ 7
Bluetooth: Core ver 2.15
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: Generic Bluetooth USB driver ver 0.5
usbcore: registered new interface driver btusb
phy0: Selected rate control algorithm 'minstrel'
ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70)
Clocksource tsc unstable (delta = -413442562 ns)
lp: driver loaded but no devices found
evdev.c(EVIOCGBIT): Suspicious buffer size 511, limiting output to 64 bytes. See http://userweb.kernel.org/~dtor/eviocgbit-bug.html
usb 1-2: USB disconnect, address 2
usb 1-2: new high speed USB device using ehci_hcd and address 7
usb 1-2: configuration #1 chosen from 1 choice
scsi4 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 7
usb-storage: waiting for device to settle before scanning
usb 1-2: USB disconnect, address 7
usb 2-2: new full speed USB device using uhci_hcd and address 2
usb 2-2: configuration #3 chosen from 1 choice
cdc_acm 2-2:3.1: ttyACM0: USB ACM device
cdc_wdm 2-2:3.7: cdc-wdm0: USB WDM device
cdc_acm 2-2:3.3: ttyACM1: USB ACM device
usbcore: registered new interface driver cdc_wdm
usbcore: registered new interface driver cdc_acm
cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapter s
usb0: register 'cdc_ether' at usb-0000:00:1d.0-2, CDC Ethernet Device, 02:80:37: 0e:03:00
usbcore: registered new interface driver cdc_ether
PPP generic driver version 2.4.2
PPP BSD Compression module registered
PPP Deflate Compression module registered
ip_tables: (C) 2000-2006 Netfilter Core Team
nf_conntrack version 0.5.0 (8056 buckets, 32224 max)
CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
nf_conntrack.acct=1 kernel paramater, acct=1 nf_conntrack module option or
sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
usb 1-5: reset high speed USB device using ehci_hcd and address 5
usb 1-5: reset high speed USB device using ehci_hcd and address 5
usb 1-5: reset high speed USB device using ehci_hcd and address 5
usb 1-5: reset high speed USB device using ehci_hcd and address 5
usb 1-5: reset high speed USB device using ehci_hcd and address 5
usb 1-5: reset high speed USB device using ehci_hcd and address 5
usb 1-5: reset high speed USB device using ehci_hcd and address 5
#
Code: Select all
# ./bluetooth
+ killall dbus-launch
+ killall bluetoothd
+ killall bluetooth-applet
killall: bluetooth-applet: no process killed
+ killall obexd
killall: obexd: no process killed
+ /etc/init.d/dbus restart
Stopping system message bus...
15518 ? Zs 0:00 dbus-daemon <defunct>
+ sleep 1
+ mkdir /root/bluetooth-share
+ bluetoothd -n
bluetoothd[16041]: Bluetooth daemon 4.61
bluetoothd[16041]: Unable to get on D-Bus
+ /usr/libexec/obexd --ftp --opp -r /root/bluetooth-share -n
+ sleep 1
Failed to connect to socket /tmp/dbus-eJIZiklUb0: Connection refused
obexd[16042]: manager_init failed
+ bluetooth-applet
# Can't get session bus: Failed to connect to socket /tmp/dbus-eJIZiklUb0: Connection refused
Code: Select all
Bluetooth: Generic Bluetooth USB driver ver 0.5
i801_smbus 0000:00:1f.3: PCI INT B -> Link[LNKD] -> GSI 7 (level, low) -> IRQ 7
usbcore: registered new interface driver btusb
phy0: Selected rate control algorithm 'minstrel'
ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70)
Clocksource tsc unstable (delta = -300472249 ns)
lp: driver loaded but no devices found
evdev.c(EVIOCGBIT): Suspicious buffer size 511, limiting output to 64 bytes. See http://userweb.kernel.org/~dtor/eviocgbit-bug.html
usbcore: registered new interface driver cdc_acm
cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapter s
bluetooth-wizar[12453]: segfault at 0 ip b7e5e980 sp bf908e60 error 4 in libdbus -1.so.3.4.0[b7e54000+35000]
PPP generic driver version 2.4.2
Posted: Sat 13 Mar 2010, 04:45
by jemimah
Dbus crashing again, weird since it's the same dbus package I used last time - just changed it to use a proper init script. Using the same script on Puppeee with no issues.