Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 71755 - obexftp complains about Connecting...failed: connect
Summary: obexftp complains about Connecting...failed: connect
Status: RESOLVED WORKSFORME
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All All
: High normal (vote)
Assignee: Alin Năstac (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-19 07:18 UTC by Karl Trygve Kalleberg (RETIRED)
Modified: 2006-06-12 06:19 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Karl Trygve Kalleberg (RETIRED) gentoo-dev 2004-11-19 07:18:45 UTC
My machine is configured with IrDA:

1) kernel: 2.6.8-gentoo-r3, modules irda, irtty_sir, sir_dev
2) net-wireless/irda-utils-0.9.16
3) net-wireless/obexftp-0.10.4

irdadump tells me that the laptop can see the cell phone:
15:19:53.210451 xid:rsp 01f7d1a4 < 07077000 S=6 s=5 SIEMENS S65 hint=b124 [PnP Modem Fax IrCOMM IrOBEX ] (28)

ifconfig tells me:
irda0     Link encap:IrLAP  HWaddr 00:00:00:00
          UP RUNNING NOARP  MTU:2048  Metric:1
....

However, when I try obexftp -l, I only get:
No custom transport
Connecting...failed: connect
Still trying to connect
Connecting...failed: connect
Still trying to connect
Connecting...failed: connect
Still trying to connect

The KDE OBEX devices control center plugin has no problems finding and configuring the phone.

Is our obexftp package on the fritz? Please advice.
Comment 1 Andrej Kacian (RETIRED) gentoo-dev 2005-01-05 11:44:31 UTC
Is this still an issue with 0.10.6?

I'm only using obexftp over Bluetooth (usually with my Siemens S55), so I'm afraid I'm not much help with irda connections, until I buy an IrDA for my linux box, sorry.
Comment 2 Jaroslav Barton 2005-01-26 12:40:08 UTC
if I edit makefile for irdadump autoconf=autoconf-2.59 then irdadump is compiled succesfully
Comment 3 Korsani 2005-12-21 13:30:50 UTC
Same problem, but I found ... a kind of workaround :)

Here is a strace:

execve("/usr/bin/obexftp", ["obexftp", "-i", "-l"], [/* 68 vars */]) = 0
uname({sys="Linux", node="rynn", ...})  = 0
brk(0)                                  = 0x804c000
access("/etc/ld.so.preload", R_OK)      = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY)      = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=59429, ...}) = 0
mmap2(NULL, 59429, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7f57000
close(3)                                = 0
open("/usr/lib/libopenobex-1.0.so.1", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0 #\0\000"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=31684, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7f56000
mmap2(NULL, 30780, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb7f4e000
mmap2(0xb7f55000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x6) = 0xb7f55000
close(3)                                = 0
open("/usr/lib/libbluetooth.so.1", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\3004\0"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=68932, ...}) = 0
mmap2(NULL, 71472, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb7f3c000
mmap2(0xb7f4c000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xf) = 0xb7f4c000
close(3)                                = 0
open("/usr/lib/libobexftp.so.0", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0`\25\0\000"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=18512, ...}) = 0
mmap2(NULL, 16896, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb7f37000
mmap2(0xb7f3b000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x4) = 0xb7f3b000
close(3)                                = 0
open("/usr/lib/libcobexbfb.so.0", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\200\10"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=5496, ...}) = 0
mmap2(NULL, 8152, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb7f35000
mmap2(0xb7f36000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0) = 0xb7f36000
close(3)                                = 0
open("/usr/lib/libbfb.so.0", O_RDONLY)  = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\220\f\0"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=10460, ...}) = 0
mmap2(NULL, 12992, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb7f31000
mmap2(0xb7f34000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2) = 0xb7f34000
close(3)                                = 0
open("/lib/libc.so.6", O_RDONLY)        = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\271U\1"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=1166880, ...}) = 0
mmap2(NULL, 1113396, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb7e21000
mprotect(0xb7f2a000, 27956, PROT_NONE)  = 0
mmap2(0xb7f2b000, 16384, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x109) = 0xb7f2b000
mmap2(0xb7f2f000, 7476, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7f2f000
close(3)                                = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7e20000
mprotect(0xb7f2b000, 4096, PROT_READ)   = 0
mprotect(0xb7f7b000, 4096, PROT_READ)   = 0
munmap(0xb7f57000, 59429)               = 0
open("/dev/urandom", O_RDONLY)          = 3
read(3, "\4\6\340-", 4)                 = 4
close(3)                                = 0
write(2, "No custom transport\n", 20No custom transport
)   = 20
brk(0)                                  = 0x804c000
brk(0x806d000)                          = 0x806d000
rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_DFL}, 8) = 0
write(2, "Connecting...", 13Connecting...)           = 13
socket(PF_BLUETOOTH, SOCK_STREAM, 3)    = -1 EAFNOSUPPORT (Address family not supported by protocol)
socket(PF_BLUETOOTH, SOCK_STREAM, 3)    = -1 EAFNOSUPPORT (Address family not supported by protocol)
write(2, "failed: connect\n", 16failed: connect                                         
)       = 16                                                                            
write(2, "Still trying to connect\n", 24Still trying to connect                         
) = 24                                                                                  
write(2, "Connecting...", 13Connecting...)           = 13                               
socket(PF_BLUETOOTH, SOCK_STREAM, 3)    = -1 EAFNOSUPPORT (Address family not supported by protocol)
socket(PF_BLUETOOTH, SOCK_STREAM, 3)    = -1 EAFNOSUPPORT (Address family not supported by protocol)
write(2, "failed: connect\n", 16failed: connect                                         
)       = 16                                                                            
write(2, "Still trying to connect\n", 24Still trying to connect                         
) = 24                                                                                  
write(2, "Connecting...", 13Connecting...)           = 13                               
socket(PF_BLUETOOTH, SOCK_STREAM, 3)    = -1 EAFNOSUPPORT (Address family not supported by protocol)
socket(PF_BLUETOOTH, SOCK_STREAM, 3)    = -1 EAFNOSUPPORT (Address family not supported by protocol)
write(2, "failed: connect\n", 16failed: connect                                         
)       = 16                                                                            
write(2, "Still trying to connect\n", 24Still trying to connect                         
) = 24                                                                                  
exit_group(1)


After seeing at sources, I think the faulty lines in obexftp/client.c are these:

#ifdef HAVE_BLUETOOTH
        cli->obexhandle = OBEX_Init(OBEX_TRANS_BLUETOOTH, cli_obex_event, 0);
#else   
        cli->obexhandle = OBEX_Init(OBEX_TRANS_IRDA, cli_obex_event, 0);
#endif

that mean that even if irda is present, if obexftp is compiled with bluetooth, it will use bluetooth sockets.
Actually, I looked at the original sources and lines are the sames although it works (use irda when I specify -i). That why I suspect bug on gentoo, not on obexftp.
Two workarounds:
1- Compile from real sources
2- emerge --unmerge bluez-libs; emerge obexftp ; emerge bluez-libs. So that obexftp won't find bluetooth/bluetooth.h and won't link against. Of course, no BT will be available anymore :)
Comment 4 Alin Năstac (RETIRED) gentoo-dev 2006-06-04 06:58:22 UTC
Actually, if you want to disable bluetooth support in obexftp, is sufficient to build it with bluetooth flag disabled.

Maybe this bug should be closed. I cannot test it on irda (I myself am a bluetooth user only) but there is not too much action anyway so I guess it isn't a widespread issue.
Comment 5 Alin Năstac (RETIRED) gentoo-dev 2006-06-11 05:48:24 UTC
closed due to bug inactivity.
Comment 6 Korsani 2006-06-12 03:45:23 UTC
Not ok for closing!
I have bluetooth AND irda because my mouse/keyboard are bluetooth, and my phone is irda only. So I NEED obexftp to be irda AND bluetooth!
Recompiling obexftp each time I need to use irda instead of BT is not a good way of solving this issue.
Comment 7 Alin Năstac (RETIRED) gentoo-dev 2006-06-12 04:37:48 UTC
1) Please define "real source"
2) Have you tried the latest obexftp? Your comment about obexftp/client.c isn't true for version 0.21.
Comment 8 Korsani 2006-06-12 06:19:38 UTC
Ahum...
Mmmm....
Oki doki. Shame on me: I didn't tried the latest version. And I won't be able to: my phone (the only things that I need irda for) has no more irda (broken)
Be sure I'll try if I found an irda phone :)