[gnome-bluetooth] libbtctl, gnome-bluetooth, gnome-phone-manager & Gentoo

[Tom Wesley]

On Sat, 2004-06-19 at 23:06 +0200, Richard Torkar wrote:
> Hi all,
> 
> just wanted to give you a heads up on all the ebuilds I've prepeared for
> gentoo. Hopefully they will be included into portage a.s.a.p.
> 
> The ebuilds incl. patch, for libbtctl-0.4.1 and gnome-bluetooth-0.5.1
> can be found at:
> http://bugs.gentoo.org/show_bug.cgi?id=53549
> 
> gnome-phone-manager-0.3:
> http://bugs.gentoo.org/show_bug.cgi?id=54448
> 
> The only thing one needs to think about is that the rfcomm.ko kernel
> module is loaded into the kernel and that /dev/rfcomm[0-9] have the
> right permissions so that a regular user can read/write to that
> interface.
> 
> BTW Edd - gnome-phone-manager works great on gentoo!
> 
> /Richard

Everything works great on Gentoo, just takes some work somtimes ;)

Onto the "some work" section:

I'm using a Nokia 6820 and have just emerged the above ebuild (slight
adjustment to gnome-phone-manager ebuild, see bug).  It works OK for
sending messages, but dies when a message is received.

Bug-buddy - backtrace was generated from '/usr/bin/gnome-phone-manager'

Using host libthread_db library "/lib/libthread_db.so.1".
0x40bc994b in waitpid () from /lib/libpthread.so.0
#0  0x40bc994b in waitpid () from /lib/libpthread.so.0
#1  0x400f7098 in ?? () from /usr/lib/libgnomeui-2.so.0

And the output on the console:

conn_complete:  status 0x00
Browsing 00:02:EE:D0:9B:C1 ...
Service Name: Dial-up networking
Service RecHandle: 0x10002
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 1
Service Class ID List:
  "Dialup Networking" (0x1103)
  "Generic Networking" (0x1201)
** Message: device 00:02:EE:D0:9B:C1 (Dialup Networking) port 1

** Message: device 00:02:EE:D0:9B:C1 (Generic Networking) port 1


Browsing 00:02:EE:D0:9B:C1 ...
Service Name: Dial-up networking
Service RecHandle: 0x10002
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 1
Service Class ID List:
  "Dialup Networking" (0x1103)
  "Generic Networking" (0x1201)
** Message: device 00:02:EE:D0:9B:C1 (Dialup Networking) port 1

** Message: device 00:02:EE:D0:9B:C1 (Generic Networking) port 1


** Message: rfcomm attempting to connect 00:02:EE:D0:9B:C1 chan 1, got 0
** Message: Waiting for udev device to appear
** Message: New connection device is /dev/rfcomm0
** Message: Connecting...
** Message: Status 1
** Message: Making serial port connection
** Message: Status 2
** Message: Serial port connected
** Message: Connected to device on /dev/rfcomm0
** Message: Exiting connect thread
** Message: Queued message to 07736839014
** Message: Sending message to 07736839014
** Message: Message sent
** Message: SMS message received

Anyone have any ideas?

-- 
Tom Wesley <tom.wesley at ntlworld.com>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.usefulinc.com/pipermail/gnome-bluetooth/attachments/20040620/b137d395/attachment.pgp