Page 2 of 6 FirstFirst 1 2 3 4 ... LastLast
Results 11 to 20 of 55

Thread: OS X (10.10.1) Fieryd keeps crashing & reloading constantly

  1. #11
    Join Date
    Dec 2010
    Location
    Switzerland
    Posts
    4

    Default Same issue

    Hi Greta

    Im getting the same issue. Please, is it possible to have this patch.

    Best regards

  2. #12
    Join Date
    Jul 2009
    Location
    Amsterdam
    Posts
    963

    Default

    Here's a link to a patch for you to try.
    Just simply install it over the top.

    https://www.dropbox.com/s/4qes3pkipv...9.dmg.zip?dl=0

    Let us know how it goes.

    Greta.

  3. #13
    Join Date
    Jan 2015
    Posts
    10

    Default

    Greta,

    This second patch, does it require the first patch to be applied before it, or does this second patch include everything that the first patch did (so that it is only necessary to install the original driver and then this second patch, with the first patch not being needed)?

    EDIT: It seems i was mistaken - the file you linked to above seems to be the same as the first patch from the 9th of janary (effectively meaning there's only one patch so far). As I've written a few days ago, after applying that patch the original error/frequent crash is gone, but we now have another crash happening over and over again (slightly less frequently, but still with just a few seconds apart). We need that patched too. It's cluttering our logs very much. Thanks.
    Last edited by abcdef; 01-23-2015 at 03:01 AM.

  4. #14
    Join Date
    Jan 2015
    Posts
    10

    Default

    Any progress on this? The new errors/crashing is still going on, with a few seconds apart.

  5. #15
    Join Date
    Jul 2009
    Location
    Amsterdam
    Posts
    963

    Default

    abcdef - what is this new error you are referring to?

    "but we now have another crash happening over and over again (slightly less frequently, but still with just a few seconds apart). We need that patched too."

    Can you send me details?

  6. #16
    Join Date
    Jan 2015
    Posts
    3

    Default Joining in—same issues

    Hey all. We've been dealing with the same issue. We were getting the constant, repeating fierybidi crash.

    Here's our error log. Note we removed the XML data. It seems this is a situation where it's calling for a version from the OS and getting an unexpected answer? Maybe a deprecated call to the OS?

    Code:
    1/27/15 6:17:50.651 PM fierybidi[46044]: WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.2 instead of 10.10.2. Use NSProcessInfo's operatingSystemVersion property to get correct system version number.
    Call location:
    1/27/15 6:17:50.652 PM fierybidi[46044]: 0   CarbonCore                          0x00007fff8e3ebd9b ___Gestalt_SystemVersion_block_invoke + 113
    1/27/15 6:17:50.652 PM fierybidi[46044]: 1   libdispatch.dylib                   0x00007fff9444dc13 _dispatch_client_callout + 8
    1/27/15 6:17:50.652 PM fierybidi[46044]: 2   libdispatch.dylib                   0x00007fff9444db26 dispatch_once_f + 117
    1/27/15 6:17:50.652 PM fierybidi[46044]: 3   CarbonCore                          0x00007fff8e3943ca _Gestalt_SystemVersion + 987
    1/27/15 6:17:50.652 PM fierybidi[46044]: 4   CarbonCore                          0x00007fff8e393fb7 Gestalt + 144
    1/27/15 6:17:50.652 PM fierybidi[46044]: 5   libefijp2.dylib                     0x000000010ecca906 _Z14wxGetOsVersionPiS_ + 31
    1/27/15 6:17:50.652 PM fierybidi[46044]: 6   libefijp2.dylib                     0x000000010ed247d3 _ZNK14wxGUIAppTraits17GetToolkitVersionEPiS0_ + 15
    1/27/15 6:17:50.900 PM fierybidi[46044]: gszXMLData = XML data Removed
    
    1/27/15 6:17:51.058 PM fierybidi[46044]: FieryCFFilter:LoadJPModuleEx::pGetServerValueFromDict:::error=-18
    1/27/15 6:17:51.124 PM fierybidi[46044]: [ColorWise:LoadJPModule] PPD Message Write - START
    1/27/15 6:17:51.125 PM fierybidi[46044]: [AllDeviceLinkProfiles:LoadJPModule] PPD Message Write - START
    1/27/15 6:17:51.126 PM fierybidi[46044]: [AllDeviceLinkProfiles:LoadJPModule] PPD Message Write - END

  7. #17
    Join Date
    Jan 2015
    Posts
    10

    Default

    Quote Originally Posted by Greta_C View Post
    abcdef - what is this new error you are referring to?

    "but we now have another crash happening over and over again (slightly less frequently, but still with just a few seconds apart). We need that patched too."

    Can you send me details?
    Greta,

    I mean the one that I posted in this thread over a week ago. This is the URL to the post I made, it has a log snippet attached as a file: http://fieryforums.efi.com/showthrea...6069#post16069

    We'd really appreciate this moving forward as quickly as possible. We are beginning to regret purchasing two expensive Xerox printers, as the drivers for them (EFI ones) are just a pain as it is now. The problem is the crashes, and when it's not crashing it's slow. We had an old HP previously which just worked perfectly for ten years. Haven't had anything but problems with this new stuff.

    Please let me know if there's any other log you need in relation to the error in the log snippet I supplied. I can reproduce that error any minute of the week if needed and will help as much as I can to get this resolved.

    Thank you!

  8. #18
    Join Date
    Jul 2009
    Location
    Amsterdam
    Posts
    963

    Default

    Sorry abcdef I didn't see your attached file before. We're looking into it now.
    Apologies for the inconvenience.

  9. #19
    Join Date
    Jul 2009
    Location
    Amsterdam
    Posts
    963

    Default

    abcdef and abordner,

    Our engineers have looked into the problem reported, and can see that the version selector is calling an error in terminal - however the driver itself is not crashing. The error is harmless, everything should be fully functional.

    Can you let us know if this is the case? Can you open the full properties of the driver?

    Thanks,

    Greta.

  10. #20
    Join Date
    Jan 2015
    Posts
    10

    Default

    Hi Greta,

    Thanks for looking into it. Can you clarify what information you'd like us/me to provide:

    > Can you let us know if this is the case?
    Let you know if what is the case?

    > Can you open the full properties of the driver?
    Not sure what you mean, can you elaborate on what information you are looking for/where we can retreive it?

    On a general note, it's a problem that the logs getting this stuff all the time, because I'm trying to debug some other issues (unrelated, with Yosemite 10.10 in general) and it's hard to follow the logs when this is taking up 95% of them

    Thanks!

Page 2 of 6 FirstFirst 1 2 3 4 ... LastLast

Posting Permissions

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