Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 239189 - Server not reachable after a bluetooth restart
Server not reachable after a bluetooth restart
Product: Fedora
Classification: Fedora
Component: gnome-bluetooth (Show other bugs)
x86_64 Linux
medium Severity low
: ---
: ---
Assigned To: Ondrej Vasik
Depends On:
  Show dependency treegraph
Reported: 2007-05-05 16:19 EDT by Jan Kratochvil
Modified: 2007-11-30 17:12 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-07-23 05:58:09 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Bugzilla 309232 None None None Never

  None (edit)
Description Jan Kratochvil 2007-05-05 16:19:12 EDT
Description of problem:
After `service bluetooth restart' I have to restart by hand `gnome-obex-server'
otherwise mobile phone rejects any upload to PC (mobile->PC).

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Start machine (both bluetooth service and the gnome-obex-server get started).
2. service bluetooth restart
3. Click bluetooth send to PC on your mobile phone.

Actual results:
Very fast Bluetooth connection failed.

Expected results:
Sent file.

Additional info:
After clicking `Quit.' and starting `Applications->System Tools->Bluetooth File
Sharing' again everything works fine.
I believe it may start in the inappropriate order during system start but I do
not have confirmed it.
According to netstat(1) the connection to UNIX socket `/var/run/sdp' is broken /
is not connected after `service bluetooth restart'.
Comment 1 Bastien Nocera 2007-07-23 05:58:09 EDT
Known upstream bug:

Note You need to log in before you can comment on or make changes to this bug.