Bug 754469

I can confirm this bugreport -- F16, same Samsung GT-B2710 phone.

[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

It worked for me in F16, but now in F17 not. Similar problems:

(In reply to comment #0)
> Version-Release number of selected component (if applicable):
> 
> This is fedora 16 with all updates installed as of 2011-11-16

Mine is Fedora 17, also fully updated.

> Steps to Reproduce:
> 1. Click on the bluetooth icon in the notification area and select "Setup a
> new device" while making sure that the phone bluetooth visibility is on. 
> 2. Click continue in the dialog that appears and then select the phone from
> the list of the discovered devices. Perform device pairing.
> 3. After that the system show a dialog asking about possibility to "Access
> the Internet using your mobile phone (DUN)". Click on that option.

I cannot even get to the 3rd step, as the 2nd stucks the configure wizard. However, I can close the wizard and the phone has been added, so I click it and click on DUN connection, and then the window closes and no connection happens.

> Actual results:
> 
> The dialog shows "Permission Denied (13)".

I get all of your errors except for this one.

> Here is relevant /var/log/messages log:
> ...

Mine:

Jun 13 14:38:36 localhost dbus-daemon[656]: dbus[656]: [system] Rejected send message, 3 matched rules; type="method_return", sender=":1.73" (uid=1000 pid=1597 comm="bluetooth-wizard ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.0" (uid=0 pid=549 comm="/usr/sbin/bluetoothd -n ")
Jun 13 14:38:36 localhost dbus[656]: [system] Rejected send message, 3 matched rules; type="method_return", sender=":1.73" (uid=1000 pid=1597 comm="bluetooth-wizard ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.0" (uid=0 pid=549 comm="/usr/sbin/bluetoothd -n ")
Jun 13 14:38:37 localhost bluetoothd[549]: bluetoothd[549]: input-headset driver probe failed for device 0C:DD:EF:DE:FC:62
Jun 13 14:38:37 localhost bluetoothd[549]: input-headset driver probe failed for device 0C:DD:EF:DE:FC:62

As a workaround I installed KDE. There the phone paired and DUN networking has been working without any problems. After that I can activate the phone from Gnome.

So this is pure Gnome issue.

With all updates as of 2012-07-31 the bug still exists. However, the symptoms changed. Now after clicking:

"Access the Internet using your mobile phone (DUN)"

the dialog shows "Detecting phone configuration" and then timeouts with the message:

"Error: timed out detecting phone details."

The bottom line is the same: I cannot setup with Gnome DUN connection with the phone. But with KDE this works.

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

This is still not working in F18.

I just want to share my experience with this issue:

- Fedora 18 fully updated
- Gnome Shell
- 2 mobile phones: Nokia C5 and Samsung Galaxy S2 GT-I9100

Test with Nokia C5
------------------
1) Enable bluetooth in the mobile phone connection settings
2) From the Bluetooth's icon in Gnome, click on 'Setup a New Device' and wait to appear the desired device
3) Once detected, select it and press 'Continue'
4) Accept the number for pairing request and click on 'Matches'
5) In the next step click on 'Access the Internet using your mobile phone (DUN)'
        ... Detecting phone configuration ...

6) New Mobile Broadband Connection
        This assistant helps you to easily set up a mobile broadband connection to a cellular (3G) network:
        ...
        ...
        ... just click on 'Continue'
7) Select the Country or region and click 'Continue'
8) Select your Provider and click 'Continue'
9) Select your plan and click 'Continue'
10) The last window shows a summary of the settings, so just click on 'Apply'

Now I can see a new network interface called "Mobile broadband" in the Network settings.

All worked finelly!


Test with Samsung Galaxy S2 GT-I9100
------------------------------------
(using PdaNet 3.50 free app)

1) Open PdaNet app and tap on 'Bluetooth DUN Mode'
2) In the next screen tap on 'Activate Bluetooth DUN' and press 'Yes'
3) From the Bluetooth's icon in Gnome, click on 'Setup a New Device' and wait to appear the desired device
4) Once detected, select it and press 'Continue'
5) Accept the number for pairing request and click on 'Matches'
6) In the next step click on 'Access the Internet using your mobile phone (DUN)'
        ... Detecting phone configuration ...
   and finally
        Error: timed out detecting phone details.


Now the details of the DUN (Dial-Up Networking) Service offered by each mobile phone:

[root@localhost ~]# hcitool scan
Scanning ...
	**:F4:19:70:5B:**	Nokia C5-00.2
	**:51:03:F3:52:**	GT-I9100


[root@localhost ~]# sdptool search DUN
Inquiring ...
Searching for DUN on **:F4:19:70:5B:** ...
Service Name: Dial-Up Networking
Service RecHandle: 0x10013
Service Class ID List:
  "Dialup Networking" (0x1103)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 5
Language Base Attr List:
  code_ISO639: 0x454e
  encoding:    0x6a
  base_offset: 0x100
Profile Descriptor List:
  "Dialup Networking" (0x1103)
    Version: 0x0100

Searching for DUN on **:51:03:F3:52:** ...
Service Name: Dial-up networking (DUN)
Service RecHandle: 0x1000a
Service Class ID List:
  UUID 128: 00001103-0000-1000-8000-00805f9b34fb
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 4


As you can see there is a big difference in how the DUN service is offered between the two mobile phones.

I think that the UUID could be the cause of why Gnome is unable to determine de DUN service on a Samsung Galaxy S2 GT-I9100 and perhaps in other Samsung mobiles.

I hope all this helped to fix it.