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

I'm having the same problem with openSuse 13.1. I'm using Flirc-v1.2.2-x64. I've got libusb-1_0-0-1.0.9-8.1.2.x86_64.rpm installed, as well as every other rpm beginning with "libusb". Doing "nm -D /usr/lib64/libusb-1.0.so.0.1.0" shows several other functions beginning with libusb, so I'm guessing I need a newer version of the libusb libraries.

 

~/Flirc-v1.2.2-x64> nm -D /usr/lib64/libusb-1.0.so.0.1.0 |grep libusb_get

0000000000004e20 T libusb_get_active_config_descriptor

0000000000003140 T libusb_get_bus_number

0000000000004fb0 T libusb_get_config_descriptor

0000000000005230 T libusb_get_config_descriptor_by_value

0000000000004170 T libusb_get_configuration

0000000000003410 T libusb_get_device

0000000000003150 T libusb_get_device_address

0000000000004d40 T libusb_get_device_descriptor

00000000000032a0 T libusb_get_device_list

0000000000003160 T libusb_get_device_speed

0000000000003b30 T libusb_get_max_iso_packet_size

0000000000003ab0 T libusb_get_max_packet_size

00000000000062d0 T libusb_get_next_timeout

0000000000006af0 T libusb_get_pollfds

00000000000052b0 T libusb_get_string_descriptor_ascii

0000000000004400 T libusb_get_version

~/Flirc-v1.2.2-x64> 

Replying to my own post, I was able to download source at                  Download libusb-1.0.18.tar.bz2 (502.2 kB)              and compile it, but it installs to /usr/local/lib64 which is not part of the standard search path. I got it to run LD_LIBRARY_PATH, but I'd really like to find at least a src rpm instead.

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.