After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 667869 - Reconnection not possible with Nokia C7-00 DUN over bluetooth
Reconnection not possible with Nokia C7-00 DUN over bluetooth
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: ModemManager
0.5.x
Other Linux
: Normal normal
: ---
Assigned To: Dan Williams
Depends on:
Blocks:
 
 
Reported: 2012-01-13 14:00 UTC by Vaclav Smilauer
Modified: 2012-02-20 07:17 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
startup log of modem-manager --debug (6.72 KB, text/x-log)
2012-01-13 14:00 UTC, Vaclav Smilauer
Details
Log of the first (successful) connection from modem-manager (22.84 KB, text/x-log)
2012-01-13 14:01 UTC, Vaclav Smilauer
Details
modem-manager log when the computer is suspended (1.65 KB, text/x-log)
2012-01-13 14:02 UTC, Vaclav Smilauer
Details
modem-manager failed reconnection log, after resuming from suspend (28.89 KB, text/x-log)
2012-01-13 14:03 UTC, Vaclav Smilauer
Details
NM_PPP_DEBUG=1 NetworkManager --no-daemon log (some lines related to irrelevant wlan0 interface deleted) (15.29 KB, text/x-log)
2012-01-13 14:10 UTC, Vaclav Smilauer
Details

Description Vaclav Smilauer 2012-01-13 14:00:09 UTC
This bug looks similar to #650740: DUN over bluetooth only works the first time the device connects. When reconnecting (e.g. after computer resumes from suspend), there is an error. I attach logs output by modem-manager --debug on the console.

1. mm-startup.log is the logfile up to dialing up the connection
2. mm-conn-ok.log is the first connection, which succeeds
3. mm-sleep.log is when the computer is suspended
4. mm-conn-error.log is reconnection attempt after resuing the computer

The nm.log is NM_PPP_DEBUG=1 NetworkManager --no-daemon log; I deleted some lines related to wlan0 which got active in-between. The first and second connection attempts can be found by looking for lines with "starting connection 'Vodafone Predefinito'", which appears twice: first for the successful, second for the unsuccessful connection attempt.

I can provide any other diagnostics necessary. The phone was showing the same problem with 2 different carriers & SIM cards (Vodafone Czech Republic, Orange Austria); another Samsung phone was reconnecting flawlessly with the same carrier.
Comment 1 Vaclav Smilauer 2012-01-13 14:00:54 UTC
Created attachment 205193 [details]
startup log of modem-manager --debug
Comment 2 Vaclav Smilauer 2012-01-13 14:01:32 UTC
Created attachment 205195 [details]
Log of the first (successful) connection from modem-manager
Comment 3 Vaclav Smilauer 2012-01-13 14:02:17 UTC
Created attachment 205196 [details]
modem-manager log when the computer is suspended
Comment 4 Vaclav Smilauer 2012-01-13 14:03:05 UTC
Created attachment 205197 [details]
modem-manager failed reconnection log, after resuming from suspend
Comment 5 Vaclav Smilauer 2012-01-13 14:09:44 UTC
To clarify further: the first connection after the phone startup is successful, any connection afterwards fail. When the phone is rebooted, modem connects fine the first time again, then gives errors again.
Comment 6 Vaclav Smilauer 2012-01-13 14:10:59 UTC
Created attachment 205201 [details]
NM_PPP_DEBUG=1 NetworkManager --no-daemon log (some lines related to irrelevant wlan0 interface deleted)
Comment 7 Aleksander Morgado 2012-01-13 14:27:25 UTC
If you know how to do it, just grab the patch from this email and you'll get it working always:

http://mail.gnome.org/archives/networkmanager-list/2012-January/msg00028.html

You're affected by the echo-garbage I talk about in that email.
Comment 8 Vaclav Smilauer 2012-01-13 15:22:10 UTC
Confirming Aleksander's patch works.
Comment 9 Aleksander Morgado 2012-02-20 07:16:41 UTC
Fixed in commit 415e8e1da85239a7dacbba328d513130c8f5d935.

This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.