Puppy Linux Discussion Forum

[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.

[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

[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.

[aarf]

created blank directory /var/lib/dbus/

and did the modification

[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.

[paulski]

I think its something new with Puppy 4.31 or with the 2.6.30.5 Kernel and newer.
I've tried all the pets on a clean install - no go.
I've also tried older sets of bluez obex etc. that I successfully used on older puppies (e.g 4.12) without any problems -albeit at the command line/script level.
Now none of those things work anymore.

Common to both approaches - I can scan and find Bluetooth devices via my USB dongle. Shows up fine in the bluetooth-wizard.
Connecting in any form goes bad and no notification goes through to the device to punch in a pin number.

Common errors at the command line show things like:
From passkey-agent "Can't get on system bus"
or others like rfcomm connect :"Can't connect RFCOMM socket: No route to host"
Or hcid "Unable to get on D-Bus"

Curious.....

[Pro]

Hi jemimah,
You have a DEV part of GConf and GConf-dbus for compile bluez-gnome?
Please post it on forum.

[jemimah]

The dev pet can be downloaded here:
http://www.murga-linux.com/puppy/viewtopic.php?p=343099#343099

[cklammer]

For which Puppy version is this post? Would this work on 4.10?

Just asking before I run waste time running against any walls ...

[jemimah]

I've only tested on 4.3. I'm doubtful about earlier versions, as the gtk version on 4.3 is even technically too old to run the gnome-bluetooth tools.

Something is screwy with the dbus install here too. I intend to take a look when I get a chance but I'm trying to get Puppeee to a releasable quality the moment and it's pretty much taking all my time.

[Volodya]

Hi!

I just wanted to thank the guy who put all this together.

I report these bluetooth dongles to be working:

ISSCEDRBTA 0x1131:0x1004 and
0xa12:0×1

Both generics

Worked fine for sending files from the computer to the telephone (not for receiving).

The computer is shown in the telephone's list for sending, but when I press send I get "sending failed".

Should I add the telephone's mac address to some kind of list for enabling the computer to receive files? Which one is the shared directory if I want to access to the computer from the telephone? Where to set it?

Thank you guys, you rock!

[pabloA]

Volodya.

Have you tried running this in a console -

obexfs -b [phone mac] ~/bluetooth-share

[aarf]

[linuxgnuru]

In Fedora 14, I have tangoGPS working just fine using bluetooth rfcomm with my Nokia E75 phone's GPS, just wondered how to get the bluetooth rfcomm working under puppy and if this tango will be able to use serial ports not just usb?

[jemimah]

Fluppy011 comes with both bluetooth and tango. Probably it's easiest to start there.