Jump to content
Flirc Forums


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

audio_inside's Achievements


Newbie (1/14)



  1. OK got it. If you look in your system log then you will probably be seeing error messages like the one in my first post indicating a problem with the call to qt_apple_check_os_version().
  2. Exactly what kind of error or error message do you get about the inability to install the GUI on 10.9? Does it refuse to install or does it actually CRASH after the install?
  3. Hi Jason - wonder if you ever received my info. Would still like to resurrect my Flirc :/
  4. OK thanks, I know @jason's a busy guy but maybe he will eventually weigh in here. I'm just bummed that accepting a Flirc GUI update seems to have broken my system.
  5. Really, no clues from FLIRC Staff available to help solve this problem? I'm inferring from the crash log that qt_apple_check_os_version() is failing. But I can't seem to find any hard System Compatibility info at www.flirc.tv to know if my MacOS version 10.9.5 is really too far downrev. BUMP
  6. I had a working Flirc configuration based on a (FL-09028, original Gen1?) USB Flirc dongle purchased in 2014 that had been successfully programmed using the Flirc GUI v1.3.6 (don't know what firmware that would represent) and running under MacOS 10.9.5 on a Mac Mini used as an HTPC. Had not done any Flirc reprogramming since 2015 until this week when I got my new Harmony Remote and launched Flirc to do some updates and testing. Unfortunately agreed to the Update dialog and now Flirc GUI v3.8 crashes on launch. Crash log shows Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x00007fff86d76866 __pthread_kill + 10 1 libsystem_pthread.dylib 0x00007fff8649835c pthread_kill + 92 2 libsystem_c.dylib 0x00007fff91a00b26 abort + 125 3 org.qt-project.QtCore 0x00000001024d4d0d qt_apple_check_os_version() + 317 4 org.qt-project.QtCore 0x00000001024183b9 QCoreApplicationPrivate::QCoreApplicationPrivate(int&, char**, unsigned int) + 153 5 org.qt-project.QtGui 0x0000000101d1853e QGuiApplicationPrivate::QGuiApplicationPrivate(int&, char**, int) + 14 6 org.qt-project.QtWidgets 0x00000001029c6568 QApplication::QApplication(int&, char**, int) + 56 7 com.yourcompany.Flirc 0x0000000101042e35 QtSingleApplication::QtSingleApplication(int&, char**, bool) + 69 8 com.yourcompany.Flirc 0x0000000101042ed4 QtSingleApplication::QtSingleApplication(int&, char**, bool) + 52 9 com.yourcompany.Flirc 0x0000000101046c67 main + 71 10 com.yourcompany.Flirc 0x0000000101042434 start + 52 Amazingly, Flirc remote functionality seems to still be intact! BUT, after recovering my original Flirc GUI v1.3.6, when running it says the dongle is at v3.8 but there is no other functionality to the GUI. Flirc dongle icon shows "Disconnected" and app is very flaky, usually requiring a Force-Quit. Really hoping I can get this running again without losing all my remote programming or bricking the dongle. Is there an incremental upgrade path I can take with intermediate versions of Flirc GUI without going straight to 3.8? Any help greatly appreciated!
  • Create New...