Ticket #75 (new defect)

Opened 4 years ago

Last modified 4 years ago

Impossible to get wmgui or wminput connected since Intrepid migration

Reported by: tiyakusa Owned by: dsmith
Priority: blocker Milestone:
Component: libcwiid Version: 0.6.00
Keywords: Cc:

Description

Since I migrated from Hardy to Intrepid, the lswm works well, but then trying wminput or wmgui, I always get a "Socket error" message.

I precise that it was working perfectly with Hardy before the upgrade. All Intrepid's upgrades are installed, and I checked that libbluetooth3 is used instead of libbluetooth2.

I think there is an issue in libcwiid since Intrepid.

I tried both version from repository and svn.

Change History

Changed 4 years ago by cookies

I've had the very same problem. However, the solution posted by sgt rod at http://abstrakraft.org/cwiid/discussion/1/109 might solve it.

Changed 4 years ago by r0ckarong

I just noticed while fooling around that you CAN get a connection if you run "sudo hcitool cc <MAC of Wiimote>" while wminput or wmgui is polling for the Wiimote.

Start wmgui, go into connect mode, press 1+2 on Wiimote and then run hcitool cc in su mode to get a connection. Works for me every time so I believe something is wrong with the auth process of wminput/wmgui through libcwiid

Changed 4 years ago by dsmith

  • version changed from 0.5.02 to 0.6.00

The discussion thread indicated above offers a couple of solutions - can anyone with the OS in question verify that one of them works without a workaround?

Note: See TracTickets for help on using tickets.