Jump to content
Flirc Forums

matt_garman

Members
  • Content count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About matt_garman

  • Rank
    Junior Flirc-er
  1. I tested the apt repos + install on my VMs, Mint 18.2 and Ubuntu 16.04, and they worked! Thanks Jason!
  2. @jason - so it looks like the apt repo does work with ubuntu 14.04. But it does not work with ubuntu 16.04, nor mint 18.2. So my best guess it that debian/ubuntu introduced some kind of stricter checking on repos. Can you try again with a newer ubuntu, or upgrade your install? 14.04 is fairly old at this point.
  3. Log is attached. What I did: reboot computer (figured best to start clean). Started "Flirc" GUI program, did File->Device Log and Enabled IR debugging. Then, within Kodi, I pressed the right arrow only, fifty (50) times. Even after I was done pressing the arrow key, the log continued to fill... I watched it for maybe a minute or so, thinking it would eventually stop, but it never did. So I saved it. Log file clocks in at around 8000 lines (hence the gzip). Hopefully this is helpful! Thanks! flirc_debug.20170719.txt.gz
  4. So you're saying this feature has a chance? ;) Is that for real? That's hilarious!
  5. Not sure if this is even doable, but I thought I'd ask... Rather than presenting itself to the OS as a keyboard, what if FLIRC presented itself as a generic serial device, and just passed the IR signals on to the OS? In the past, I've done exactly this with this device: USB-UIRT. Under Linux, the USB-UIRT shows up as a serial device (typically /dev/ttyUSB0). It's a "dumb" device in that it just passes the IR signals to the OS, so it's the OS's job to do something useful with them. Under Linux, you do this with LIRC. In my mind, for the FLIRC, I envision this as an "unsupported warranty-voiding community-support only advanced mode". You'd have to use the CLI tool to convert the FLIRC device to act in this manner. But as long as LIRC could recognize the signals, you have a much more generic device. There's no shortage of DIY plans for building a USB-UIRT equivalent, for not much money. As much as I love DIY electronics projects, if I could get the same result out of the box for $23 (i.e. FLIRC), I'd be really happy. :)
  6. What distribution and version are you running? Can you post the contents of /etc/os-release and /etc/debian_version? Can you also post the output of "apt-key list"? Thanks!
  7. Hi Jason, I will try the log. I also have another remote I can test with. It might be a few days (or even the weekend) before I have time to test this. I will follow-up at that time. Thanks!
  8. Remote is an Acoustic Research ARRS05G. Yes, I am pairing and using it on the same machine.
  9. I don't think that was mean---I did show steps for others to use as a workaround until the repos are fixed. Clearly it's been an issue for some folks for over a year. For what it's worth, I have a close friend who had similar issues with the RPM packages. He told me he had a dialog with you via direct email, where he offered to help re-package your RPMs and fix your repos. You agreed to the help; he said, "OK, what next?" and you never replied. Point is, you did have an opportunity to have a team. I appreciate that you are busy. But my opinion remains: I am completely sympathetic if you don't have time to make the Linux experience as polished and turn-key as on Windows, but you owe it to your customers to advertise accordingly. As a 20-year Linux user I am used to this: with much hardware, Windows support is a given, and Linux support varies from "not at all" to "best-effort" or "community support only". But the way FLIRC is currently advertised, it comes across as Linux support being the same as Windows: you have both deb and rpm repos, and a failsafe distro-independent/statically-linked Linux failsafe program. According to my friend, the RPMs are broken; clearly the apt repos are broken for at least some of us; and the failsafe is not working for me either (see above). Anyway, in your example above you are doing an upgrade, which implies you already have a working flirc package on your system. Can you apt-get remove flirc, then comment out the line in your sources.list file, and then run "apt-get clean"? The latter will clean out your apt/dpkg cache. At this point I believe your system should be in a state similar to what mine is: effectively no knowledge of the flirc software. Now un-comment the line in sources.list, and just run "apt-get update". This command will just refresh the package index/cache. I suspect this should fail the same as it did for me and others in this thread. On the other hand, if it works, then I suspect it is a nuanced difference between various distributions' apt repository requirements. Can you tell me exactly what distribution and version you are using? I am guessing Linux Mint... I'm going to install 18.2 XFCE 64bit in a virtual machine and see if the repo works for me. Edit: I just did a fresh install of Linux Mint 18.2 XFCE 64bit. I added "deb http://apt.flirc.tv/arch/x64 binary/" to my /etc/apt/sources.list file. When I ran "apt-get update", I got the same error I posted above. I now have more confidence that if you do as I suggested above (remove flirc, remove flirc repo, clean your apt cache, then re-add the repo), you'll be able to reproduce this.
  10. The same thing happens when the remote is 10 to 15 feet away from FLIRC. I put it close because I thought it might be a signal strength/integrity issue. When you say "try running as sudo", run what under sudo? To be clear, the general programming (i.e. the Flirc tool) worked just fine. I was able to successfully program both the Simple and Kodi profiles. The issue is when trying to actually use it under Kodi. To add more detail, it's very inconsistent. A few button presses might work as expected, but then another might take 10 or more presses to actually do something. Only once have I seen a queue-type behavior, where I press the button multiple times, and the GUI delays then catches up. Typically it as though the button press is ignored or not captured.
  11. You've been working on the major release for over a year? I get the same error with the apt repo: W: The repository 'http://apt.flirc.tv/arch/x64 binary/ Release' does not have a Release file. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details. The distribution-independent binary also did not work for me: matt@host:/tmp/release/linux$ md5sum ~/Downloads/Linux_Release.zip 652ca37b1a68cd031689835a4a566b2a /home/matt/Downloads/Linux_Release.zip matt@host:/tmp$ unzip ~/Downloads/Linux_Release.zip Archive: /home/matt/Downloads/Linux_Release.zip creating: release/ inflating: release/51-flirc.rules inflating: release/index.html creating: release/linux/ inflating: release/linux/Flirc inflating: release/linux/flirc_util inflating: release/markdown.css inflating: release/release_notes.md creating: release/rpi/ inflating: release/rpi/flirc_util matt@host:/tmp$ cd release/linux/ matt@host:/tmp/release/linux$ ls Flirc flirc_util matt@host:/tmp/release/linux$ md5sum ./Flirc 67d51752dea950f8e7e0bd90c48fa88e ./Flirc matt@host:/tmp/release/linux$ ./Flirc -bash: ./Flirc: No such file or directory I'd argue it's bordering on false advertising when you say "Linux support"... Yet the Debian/Ubuntu repos don't work, and neither does the supposedly failsafe static build. Here's how I got this working, for anyone else who is similarly frustrated. I'm running Ubuntu LTS 16.04.2: $ cat /etc/os-release NAME="Ubuntu" VERSION="16.04.2 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.2 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/" SUPPORT_URL="http://help.ubuntu.com/" BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/" VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial $ cat /etc/debian_version stretch/sid I downloaded the deb file explicitly, specifically http://apt.flirc.tv/arch/x64/binary/flirc_2.5.1-1_amd64.deb There are a number of dependencies required. So I installed them all manually: $ sudo apt-get install libhidapi-hidraw0 libqt4-network libqt4-svg libqt4-xml libqtcore4 libqtgui4 libqtdbus4 libmng2 libqt4-declarative qtcore4-l10n libqt4-script libqt4-sql libqt4-xmlpatterns After the dependencies were installed, I could install the flirc deb directly: $ sudo dpkg -i flirc_2.5.1-1_amd64.deb I hope this info helps others. But I also hope it doesn't justify further delaying the fix for the repos.
  12. FLIRC USB Firmware v4.1.1. Remote is an Acoustic Research ARRS05G. Using the Kodi profile. OS is Ubuntu LTS 16.04: matt@host:~$ cat /etc/os-release NAME="Ubuntu" VERSION="16.04.2 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.2 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/" SUPPORT_URL="http://help.ubuntu.com/" BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/" VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial matt@host:~$ cat /etc/debian_version stretch/sid Whenever I press a button on the remote, I'd say there's maybe a 20% chance it is recognized. In other words, it seems most button presses are ignored. This is with the FLIRC USB device plugged into the front of the PC, and me standing right in front of it, with the remote only a few inches away. Using a (wired) USB keyboard, all button presses work immediately as expected. I'm using Flirc v2.5.1, from Deb package flirc_2.5.1-1_amd64.deb (md5sum: 4ac86479eae26df57a676e9674bb699e). Simply running Flirc and then exiting prints this out to the console: matt@host:~$ Flirc Can't load 'test.ini' 00: ff ff ff ff ff ff ff ff ff ff ff ff ............ 00: ff ff ff ff ff ff ff ff ff ff ff ff ............ 00: ff ff ff ff ff ff ff ff ff ff ff ff ............ 00: ff ff ff ff ff ff ff ff ff ff ff ff ............ 00: ff ff ff ff ff ff ff ff ff ff ff ff ............ Object::connect: No such signal QCheckBox::currentIndexChanged(int) [D] lib/libflirc/flirc_driver.c fl_major_version(387): something bad happened That "something bad happened" doesn't inspire much confidence.
×