Results 1 to 10 of 20

Thread: efiLINQ crash with OS X 10.10 Yosemite

Hybrid View

  1. #1
    Andersson is offline Senior Fiery Forum Contributor Andersson is on a distinguished path
    Join Date
    May 2010
    Posts
    52

    Default efiLINQ crash with OS X 10.10 Yosemite

    Hi

    OS X shows me a crash message for efiLINQ once a day. I can't find any information at all about efiLINQ but I suppose it has something to do with EFI.

    efiLINQ_2014-10-02-105508_Mac-Pro.crash
    efiLINQ_2014-10-03-105503_Mac-Pro.crash
    efiLINQ_2014-10-04-105503_Mac-Pro.crash
    efiLINQ_2014-10-05-105503_Mac-Pro.crash
    efiLINQ_2014-10-06-105506_Mac-Pro.crash
    efiLINQ_2014-10-07-105503_Mac-Pro.crash
    efiLINQ_2014-10-08-105503_Mac-Pro.crash
    efiLINQ_2014-10-09-105508_Mac-Pro.crash
    efiLINQ_2014-10-10-105507_Mac-Pro.crash
    efiLINQ_2014-10-11-105503_Mac-Pro.crash
    efiLINQ_2014-10-12-105501_Mac-Pro.crash
    efiLINQ_2014-10-13-105508_Mac-Pro.crash
    efiLINQ_2014-10-14-105507_Mac-Pro.crash
    efiLINQ_2014-10-15-105512_Mac-Pro.crash
    efiLINQ_2014-10-16-105502_Mac-Pro.crash
    efiLINQ_2014-10-17-105508_Mac-Pro.crash
    efiLINQ_2014-10-18-105501_Mac-Pro.crash
    efiLINQ_2014-10-19-105501_Mac-Pro.crash
    efiLINQ_2014-10-20-105502_Mac-Pro.crash
    efiLINQ_2014-10-21-105502_Mac-Pro.crash
    efiLINQ_2014-10-22-105503_Mac-Pro.crash


    Process: efiLINQ [4002]
    Path: /Library/Application Support/efiLINQ/efiLINQ
    Identifier: efiLINQ
    Version: ???
    Code Type: X86-64 (Native)
    Parent Process: ??? [1]
    Responsible: efiLINQ [4002]
    User ID: 501

    Date/Time: 2014-10-22 10:55:00.836 +0200
    OS Version: Mac OS X 10.10 (14A389)
    Report Version: 11
    Anonymous UUID: 80B7263B-E3E0-37DA-782F-1410636E7DC2


    Time Awake Since Boot: 60000 seconds

    Crashed Thread: 0 Dispatch queue: com.apple.main-thread

    Exception Type: EXC_CRASH (SIGABRT)
    Exception Codes: 0x0000000000000000, 0x0000000000000000

    Application Specific Information:
    abort() called
    terminating with uncaught exception of type Poco::SystemException: System exception

  2. #2
    Join Date
    Mar 2010
    Posts
    36

    Default Same here...

    Hey,

    I'm also running 10.10 and seeing this efiLINQ crash report a lot. It 'seems' to kick in a little while after either my Mac or the printer disconnects from the network. Could just be conincidence. Not sure if this component is part of a Fiery driver or CWS? I'm currently using CWS: V5.6.0.24 - I believe there is a newer CWS available with better Yosemite support, i'm going to try that and see what happens.

  3. #3
    Andersson is offline Senior Fiery Forum Contributor Andersson is on a distinguished path
    Join Date
    May 2010
    Posts
    52

    Default

    I have the same version and auto update is not showing anything newer. Where can I find the new version?

  4. #4
    Join Date
    Nov 2005
    Location
    Fremont, CA
    Posts
    284

    Default

    This is a problem the current version of CWS5.6 has with Mac 10.10. This will be addressed in the new version of CWS5.6 we are planning to post later next week. When it is available, you will get an automatic notification via Fiery Software Manager.

    Yes, efiLINQ is a Command WorkStation component, but you should be able to continue to use Command WorkStation even if this component is no longer working.

    Sorry for the inconvenience; we're trying to get a solution to you as quickly as possible.

    -Mike

  5. #5
    Andersson is offline Senior Fiery Forum Contributor Andersson is on a distinguished path
    Join Date
    May 2010
    Posts
    52

    Default

    Thanks for the info Mike.

  6. #6
    Join Date
    Mar 2010
    Posts
    36

    Default

    Thanks Mike,

    I've updated to v5.6.0.30, no sign of the crash yet but early days. Not a problem to wait for proper 10.10 support, the crash is infrequent as best, CWS seems to work fine for now.

    Cheers

  7. #7
    Join Date
    Dec 2012
    Posts
    17

    Default

    Quote Originally Posted by Mike_R View Post
    This will be addressed in the new version of CWS5.6 we are planning to post later next week. When it is available, you will get an automatic notification via Fiery Software Manager.
    Any news on when this update will be coming out exactly?

  8. #8
    Andersson is offline Senior Fiery Forum Contributor Andersson is on a distinguished path
    Join Date
    May 2010
    Posts
    52

    Default

    An update would be nice.

    I found new updated printer drivers for Xerox 550-560 with integrated Fiery and now I have bigger problems.

    Process: fieryd [4421]
    Path: /usr/libexec/fieryd
    Identifier: fieryd

    This process it responsible for communication with the printer and it's crashing, and trying to restart indefinitely ...

    2014-11-13 14:53:31,279 com.apple.xpc.launchd[1]: (com.efi.fieryd) Service only ran for 0 seconds. Pushing respawn out by 2 seconds.
    2014-11-13 14:53:31,291 ReportCrash[4408]: Saved crash report for fieryd[4411] version 0 to /Library/Logs/DiagnosticReports/fieryd_2014-11-13-145331_Mac-Pro.crash
    2014-11-13 14:53:33,765 com.apple.xpc.launchd[1]: (com.efi.fieryd[4413]) Service exited due to signal: Abort trap: 6
    2014-11-13 14:53:33,765 com.apple.xpc.launchd[1]: (com.efi.fieryd) Service only ran for 0 seconds. Pushing respawn out by 2 seconds.
    2014-11-13 14:53:33,777 ReportCrash[4408]: Saved crash report for fieryd[4413] version 0 to /Library/Logs/DiagnosticReports/fieryd_2014-11-13-145333_Mac-Pro.crash

    ...

    The console log is printing out this error in an never ending flow. I uninstalled the printer driver and drop in pdf-files at the moment.

  9. #9
    Join Date
    Nov 2014
    Posts
    1

    Default

    Quote Originally Posted by Mike_R View Post
    This is a problem the current version of CWS5.6 has with Mac 10.10. This will be addressed in the new version of CWS5.6 we are planning to post later next week. When it is available, you will get an automatic notification via Fiery Software Manager.

    Yes, efiLINQ is a Command WorkStation component, but you should be able to continue to use Command WorkStation even if this component is no longer working.

    Sorry for the inconvenience; we're trying to get a solution to you as quickly as possible.

    -Mike
    Mike,

    Is that update ready yet? It's been nearly a month since you indicated it would be out 'later this week'.

    I am running CWS 5.6.0.24, which is the latest version available on EFI website. Someone posted that they are running 5.6.0.30, but I don't see that anywhere.

    I get the efiLINQ quit unexpectedly error several times a day, whether CWS is running or not.

    Anyway... is a resolution coming soon?

    Thanks

  10. #10
    Join Date
    Jul 2009
    Location
    Amsterdam
    Posts
    963

    Default

    This week.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts