Jump to content
Flirc Forums

Search the Community

Showing results for tags 'crash'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Flirc forums
    • Getting Started with Flirc
    • General Questions
    • How To
    • Show Off
    • Remote Controls
    • Ideas and Suggestions
    • Bugs

Found 1 result

  1. I just got my FLIRC, unpacked it, plugged it in, got the usual keyboard screen, closed that, then tried installing the latest driver from the website. But no matter what I try, the program just won't open and keeps crashing. I thought it might be a compatibility issue, since I'm on a Mac and my current OS is High Sierra. So I tried it on a different Mac that has El Capitan, but the same thing happens: the app icon bounces and then immediately closes again. The crash report says that a certain library couldn't be loaded, so I recreated the path from the report and copied the framework file in question over. That only ended up giving me another crash related to a different library, so I copied that framework file over as well, only to get the same thing happening again with another library. I kept doing this until I got a crash report without any obvious suspects. The files in question were the following: QtCore.framework QtGui.framework QtNetwork.framework QtGui.framework QtSvg.framework QtWidgets.framwork And here is an excerpt from one of the crash reports (it's the same on both my devices): "Termination Reason: DYLD, [0x1] Library missing Application Specific Information: dyld: launch, loading dependent libraries Dyld Error Message: Library not loaded: /usr/local/Cellar/qt@5.7/5.7.1/lib/QtCore.framework/Versions/5/QtCore Referenced from: /Applications/Flirc.app/Contents/Frameworks/QtGui.framework/Versions/5/QtGui Reason: image not found" Seeing how I get the exact same issue on two individual devices, one of which is a two day old MacBook with a clean install, I think it might be an issue with the current version of the driver. I would really appreciate if someone could provide me with a version of the driver that works for them on their Apple computer, so I can troubleshoot that way. If that doesn't work either, I really have no idea what could be causing this. Would appreciate any help on this.