Ticket #144 (closed defect: fixed)

Opened 6 years ago

Last modified 4 years ago

irmc does not connect to the phone at all

Reported by: burlap@… Owned by: cstender
Priority: normal Milestone:
Component: Plugin: irmc Version: 0.20
Severity: normal Keywords:
Cc:

Description

After recent svn changes (last build as of 28.01.06), irmc does not connect via irda to my phone at all (siemens s65). Previous versions of irmc (in opensync, after lonestar patch) were able to connect (irda) and sync from phone to evolution/file-system (plugin did not write to the phone). Now all I get is:

Synchronizing group "2"
The previous synchronization was unclean. Slow-syncing
Member 1 of type irmc-sync had an error while connecting: Cannot connect via OBEX.
Member 2 of type evo2-sync just connected
Member 2 of type evo2-sync just disconnected
All clients have disconnected
The sync failed: Unable to connect one of the members
Error synchronizing: Unable to connect one of the members

At the same time obexftp works and multisync (old) discovers the phone.

I don't know whether this is my mistake or irmc problem.

Trace for irmc-member:

[1138447774.311519]     +++++++++ This is the client #1 (irmc-sync plugin) of group 2 +++++++++
[1138447775.73545]      >>>>>>>  client_message_handler(0x8061510, 0x80692b8, 0x806b2c8)
[1138447775.73709]              [CLI] DEBUG: Client message handler called for message "CONNECT"
[1138447775.73862]              >>>>>>>  osync_member_connect(0x80640e0, 0xb7efbda0, 0x80692b8)
[1138447775.74133]                      Found no IR devices.

[1138447775.74413]                      >>>>>>>  osync_context_report_osyncerror(0x806fb68, 0xb73ee238:(Cannot connect via OBEX.))
[1138447775.74648]                              [CLI] WARNING: Member is replying with message 0x806f150 to message 0x80692b8:"CONNECT" with error 1: Cannot connect via OBEX.
[1138447775.74850]                      <<<<<<<  osync_context_report_osyncerror[1138447775.74985]              <<<<<<<  osync_member_connect
[1138447775.75107]      <<<<<<<  client_message_handler

Relevant irdadump output:

13:36:25.538458 xid:rsp 0725e904 < 08364000 S=6 s=4 SIEMENS S65 hint=b124 [ PnP Modem Fax IrCOMM IrOBEX ] (28)

Config:

<config>
  <fixedst>false</fixedst>
  <donttellsync>false</donttellsync>
  <onlyphonenumbers>true</onlyphonenumbers>
  <dontacceptold>true</dontacceptold>
  <maximumage>7</maximumage>
  <translatecharset>false</translatecharset>
  <charset>ISO8859-1</charset>
  <alarmtoirmc>true</alarmtoirmc>
  <alarmfromirmc>true</alarmfromirmc>
  <convertade>false</convertade>
  <connectmedium>ir</connectmedium>
  <irname>SIEMENS S65</irname>
</config>

I can provide full logs and straces and do more testing.

Attachments

logs.tar.bz2 Download (13.4 KB) - added by burlap@… 6 years ago.
traces for irmc sync problems

Change History

Changed 6 years ago by burlap@…

traces for irmc sync problems

comment:1 Changed 5 years ago by dgollub

  • Owner changed from abauer to cstender

comment:2 Changed 5 years ago by cstender

  • Status changed from new to assigned

comment:3 Changed 5 years ago by abauer

  • Status changed from assigned to new
  • Version set to 0.20

comment:4 Changed 5 years ago by cstender

  • Status changed from new to assigned

comment:5 Changed 5 years ago by cstender

  • Status changed from assigned to new

Please try OpenSync? 0.20 and reopen this bug if your error still occurs.

comment:6 Changed 5 years ago by cstender

  • Status changed from new to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.