Re: Network-Manager Trunk and Fedora 12

[Darren Albers <dalbers gmail com>]

On Tue, Apr 6, 2010 at 3:34 AM, Dan Williams <dcbw redhat com> wrote:
> On Thu, 2010-04-01 at 08:55 -0400, Darren Albers wrote:
>> On Wed, Mar 31, 2010 at 10:02 AM, Colin Walters <walters redhat com> wrote:
>> >
>> > ----- "Dan Williams" <dcbw redhat com> wrote:
>> >
>> >> > /var/log/messages:
>> >> > Mar 25 19:51:58 localhost dbus-daemon: Rejected send message, 2
>> >> > matched rules; type="method_return", sender=":1.12" (uid=0 pid=1424
>> >> > comm="/usr/sbin/bluetoothd) interface="(unset)" member="(unset)"
>> >> error
>> >> > name="(unset)" requested_reply=0 destination=":1.10" (uid=0
>> >> pid=1414
>> >> > comm="NetworkManager))
>> >>
>> >> At what point does that failure come?  This could be caused by recent
>> >> (well, year-old) dbus policy changes for unrequested reply messages
>> >> which I'm not 100% sure how to get fixed...
>> >>
>> >> walters; what could be the cause of this sort of thing again?
>> >
>> > The operative component here is "requested_reply=0", and the policy is to reject unrequested replies.  Often this is harmless because if a message wasn't expecting a reply, denying a reply shouldn't matter.  If however the binding/code was setting no_reply AND actually expecting to process the reply, that's a bug in the calling code.
>> >
>> >
>> >
>>
>> I ran modem-manager with debug and here is the output:
>>
>> ** Message: (rfcomm0) opening serial device...
>> ** (modem-manager:2090): DEBUG: (rfcomm0): probe requested by plugin 'Generic'
>> ** (modem-manager:2090): DEBUG: (rfcomm0): --> 'AT+GCAP<CR>'
>> ** (modem-manager:2090): DEBUG: (rfcomm0): <--
>> '+GCAP:<CR><LF><CR><LF>OK<CR><LF>'
>> ** (modem-manager:2090): DEBUG: (rfcomm0): --> 'AT+GCAP<CR>'
>> ** (modem-manager:2090): DEBUG: (rfcomm0): <--
>> '+GCAP:<CR><LF><CR><LF>OK<CR><LF>'
>> ** (modem-manager:2090): DEBUG: (rfcomm0): --> 'AT+GCAP<CR>'
>> ** (modem-manager:2090): DEBUG: (rfcomm0): <--
>> '+GCAP:<CR><LF><CR><LF>OK<CR><LF>'
>> ** (modem-manager:2090): DEBUG: (rfcomm0): --> 'ATI<CR>'
>> ** (modem-manager:2090): DEBUG: (rfcomm0): <-- 'Research In Motion
>> BlackBerry IP Modem<CR><LF><CR><LF>OK<CR><LF>'
>> ** (modem-manager:2090): DEBUG: (rfcomm0): --> 'AT+CPIN?<CR>'
>> ** (modem-manager:2090): DEBUG: (rfcomm0): <-- '+CPIN:
>> READY<CR><LF><CR><LF>OK<CR><LF>'
>> ** Message: (rfcomm0) closing serial device...
>> ** Message: Generic: (tty/rfcomm0) WARNING: missing udev 'device' file
>> ** Message: (rfcomm0) opening serial device...
>> ** Message: (Generic): GSM modem
>> /sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1 claimed port rfcomm0
>> ** (modem-manager:2090): DEBUG: Added modem
>> /sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1
>> ** (modem-manager:2090): DEBUG: (rfcomm0): --> 'AT+CPIN?<CR>'
>> ** (modem-manager:2090): DEBUG: (rfcomm0): <-- '+CPIN: READY<CR><LF>'
>> ** (modem-manager:2090): DEBUG: (rfcomm0): <-- '<CR><LF>OK<CR><LF>'
>> ** Message: (rfcomm0) closing serial device...
>> ** (modem-manager:2090): DEBUG: Exported modem
>> /sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1 as
>> /org/freedesktop/ModemManager/Modems/0
>> ** Message: (rfcomm0) opening serial device...
>> ** Message: Modem /org/freedesktop/ModemManager/Modems/0: state
>> changed (disabled -> enabling)
>> ** (modem-manager:2090): DEBUG: (rfcomm0): --> 'ATZ E0 V1 +CMEE=1<CR>'
>> ** (modem-manager:2090): DEBUG: (rfcomm0): <-- '<CR><LF>ERROR<CR><LF>'
>> ** (modem-manager:2090): DEBUG: Got failure code 100: Unknown error
>> ** Message: Modem /org/freedesktop/ModemManager/Modems/0: state
>> changed (enabling -> disabled)
>> ** Message: (rfcomm0) closing serial device...
>> ** (modem-manager:2090): DEBUG: Removed modem
>> /sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1
>>
>> Looks like there is something else going on and the Blackberry
>> rejected the connection?
>
> Like you found, it probably doesn't like +CMEE=1...  guess we'll have to
> handle that somewhat differently in the generic plugin.
>
> Dan
>

Is there some alternatives you would like me to test via minicom or equivalent?