Starting sixad from QtSixA is broken

Bug #1621714 reported by James
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
QtSixA
New
Undecided
Unassigned

Bug Description

When clicking Tasks > Root Actions > Force Connection (which is supposed to fire up the sixad service), I get the message:

>The sixad driver has now been forced to start.
>You should be able to connect your devices with no problem now
(but please note that bluetooth is not workable for anything else in this mode, so you should stop sixad when you need to do something else)

However, sixad is NOT running, and if you run QtSixA from the terminal you will see it spit to stdout the help message from sixad (indicating that it was run with incorrect command-line parameters).

Revision history for this message
James (jamestheawesomedude) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.