Steve Goodey

Yes, I mentioned this in which is a shame, as it installed really easy when it was working. Let's hope the guys can get it working again. Steve.

I found that flirc was still working as a remote receiver, just that I can't now program it on my Mythbuntu system due to the above error. But moving it onto another Linux system I have, and running the Flirc GUI on that, I can program it fine. So I'm back up and running. Thanks to tjteixeira for responding. Steve.

Hello, I wonder if someone can help me? I have a Mythbuntu system where flirc was working ok. ubuntu update-manager offered some updates which I took. I know!!! Unfortunately about the same time I was trying to sort a problem with screen blanking so I don't know if something I did to do with that broke flirc. Now flirc is not working. steve@mythbuntu:~/Flirc$ ./Flirc QGtkStyle was unable to detect the current GTK+ theme. fl_open_devices(333): trying to open: 20A0 :: flirc.tv [D] fl_open_devices(379): 8087:8008 (bus 1, device 2) [D] fl_open_devices(379): 8087:8000 (bus 2, device 2) [D] fl_open_devices(379): 1241:1166 (bus 3, device 2) [D] fl_open_devices(379): 046d:0b07 (bus 3, device 3) [D] fl_open_devices(379): 2013:024f (bus 3, device 4) [D] fl_open_devices(379): 2013:024f (bus 3, device 5) [D] fl_open_devices(379): 20a0:0000 (bus 3, device 6) [D] fl_open_devices(379): 0403:6001 (bus 3, device 7) [D] fl_open_devices(379): 05e3:0722 (bus 3, device 8) [D] fl_open_devices(379): 1d6b:0002 (bus 1, device 1) [D] fl_open_devices(379): 1d6b:0002 (bus 2, device 1) [D] fl_open_devices(379): 1d6b:0002 (bus 3, device 1) [D] fl_open_devices(379): 1d6b:0003 (bus 4, device 1) [D] fl_open_devices(379): 046d:c71e (bus 3, device 9) [D] fl_open_devices(379): 046d:c71f (bus 3, device 10) fl_open_devices(333): trying to open: 20A0 :: claylogic.com [D] fl_open_devices(379): 8087:8008 (bus 1, device 2) [D] fl_open_devices(379): 8087:8000 (bus 2, device 2) [D] fl_open_devices(379): 1241:1166 (bus 3, device 2) [D] fl_open_devices(379): 046d:0b07 (bus 3, device 3) [D] fl_open_devices(379): 2013:024f (bus 3, device 4) [D] fl_open_devices(379): 2013:024f (bus 3, device 5) [D] fl_open_devices(379): 20a0:0000 (bus 3, device 6) fl_open_devices(396): claiming interface 0 [D] fl_open_devices(422): Vendor: claylogic.com [D] fl_open_devices(442): [Vendor Match] ./Flirc: symbol lookup error: ./Flirc: undefined symbol: libusb_get_port_number steve@mythbuntu:~/Flirc$ steve@mythbuntu:~/Flirc$ dmesg | grep claylogic [ 1.985896] usb 3-10: Manufacturer: claylogic.com steve@mythbuntu:~/Flirc$steve@mythbuntu:~/Flirc$ uname -a Linux mythbuntu 3.8.0-35-generic #52~precise1-Ubuntu SMP Thu Jan 30 17:24:40 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux The message about GTK+ theme is because I've ssh'd into the box to copy error message across to a laptop. Can anyone suggest what cause of undefined symbol: libusb_get_port_number is? I get the same error if I run ./Flirc as sudo Thanks, Steve

Hi, I seem to be getting a 404 error on http://apt.flirc.tv/arch/x64/binary/flirc_0.96-1_amd64.deb apt-get install flirc gives Failed to fetch http://apt.flirc.tv/arch/x64/binary/flirc_0.96-1_amd64.deb 404 Not Found Regards, Steve

Hi, Hope I haven't posted this in the wrong place. I'd just like to give a big thanks for the people involved in Flirc. I've just done a new install of Mythbuntu/Mythtv and Flirc made the remote control as easy as anything. Last time I did this I used LIRC and it was a real pain getting it to work and getting all the keys programmed. Thanks very much. Steve.