PDA

View Full Version : OS X (10.10.1) Fieryd keeps crashing & reloading constantly



ReluctantPrintAdmin
11-20-2014, 08:35 AM
Causing a CPU spike every second

Since installing the latest software/drivers 4.2.0.479
CWS 5.6.0.42a
Hot Folders 3.6.0.24
Remote Scan 6.2.0.11
Fiery 1.0.00.9

XC570-4C8B (driver version 2.0)

I've listed all I have installed but what I've heard is that 'fieryd' allows communication between Mac and printer

Got this from the console:
20/11/2014 15:33:53.925 com.apple.xpc.launchd[1]: (com.efi.fieryd[42147]) Service exited due to signal: Abort trap: 6



Any clues on how to remedy this would much appreciated

abcdef
01-07-2015, 08:44 AM
Hi there,

First off; EFI: *When* will we be able to download a fixed driver that doesn't have this problem? We reported this through our Xerox partner a month ago, and they have not yet gotten any response to it (I just asked them). We need this fixed, ASAP.

Second; EFI: Thanks a lot for logging me out after such a short time, so that I lost the text I had written in this post before the phone call I just received. You should really adjust the timeout for your forum so that it's longer.

We're having the very same problem here with a bunch of clients, all OS X 10.10. We get the same type of error messages/craches from the fieryd daemon, see below for a snippet (notice how often the crashes happen - it's basically every two seconds, continously).

The printer we installed this driver for is a Xerox WorkCentre 7845 with EFI/Fiery, and we're just adding them straight off using Bonjour, nothing fancy. The driver we're using is the latest one from EFI.com, more specifically "Xerox WorkCentre 78xx Series v1.1 Mac OS 10.6 - 10.10".

The problem for us is that the continously crashing driver slows down the computer very much, and also that the printer is effectively unusable.

Looking forward to feedback here, and a fix from EFI/Xerox.


2014-12-12 13:47:18,115 com.apple.xpc.launchd[1]: (com.efi.fieryd[1932]) Service exited due to signal: Abort trap: 6
2014-12-12 13:47:18,115 com.apple.xpc.launchd[1]: (com.efi.fieryd) Service only ran for 0 seconds. Pushing respawn out by 2 seconds.
2014-12-12 13:47:18,124 ReportCrash[1914]: Saved crash report for fieryd[1932] version 0 to /Library/Logs/DiagnosticReports/fieryd_2014-12-12-134718_Foo-Bars-computer.crash
2014-12-12 13:47:20,549 com.apple.xpc.launchd[1]: (com.efi.fieryd[1935]) Service exited due to signal: Abort trap: 6
2014-12-12 13:47:20,549 com.apple.xpc.launchd[1]: (com.efi.fieryd) Service only ran for 0 seconds. Pushing respawn out by 2 seconds.
2014-12-12 13:47:20,558 ReportCrash[1914]: Saved crash report for fieryd[1935] version 0 to /Library/Logs/DiagnosticReports/fieryd_2014-12-12-134720_Foo-Bars-computer.crash
2014-12-12 13:47:22,972 com.apple.xpc.launchd[1]: (com.efi.fieryd[1939]) Service exited due to signal: Abort trap: 6
2014-12-12 13:47:22,972 com.apple.xpc.launchd[1]: (com.efi.fieryd) Service only ran for 0 seconds. Pushing respawn out by 2 seconds.
2014-12-12 13:47:22,980 ReportCrash[1914]: Saved crash report for fieryd[1939] version 0 to /Library/Logs/DiagnosticReports/fieryd_2014-12-12-134722_Foo-Bars-computer.crash
2014-12-12 13:47:25,409 com.apple.xpc.launchd[1]: (com.efi.fieryd[1945]) Service exited due to signal: Abort trap: 6
2014-12-12 13:47:25,409 com.apple.xpc.launchd[1]: (com.efi.fieryd) Service only ran for 0 seconds. Pushing respawn out by 2 seconds.
2014-12-12 13:47:25,418 ReportCrash[1914]: Saved crash report for fieryd[1945] version 0 to /Library/Logs/DiagnosticReports/fieryd_2014-12-12-134725_Foo-Bars-computer.crash
2014-12-12 13:47:27,833 com.apple.xpc.launchd[1]: (com.efi.fieryd[1955]) Service exited due to signal: Abort trap: 6
2014-12-12 13:47:27,833 com.apple.xpc.launchd[1]: (com.efi.fieryd) Service only ran for 0 seconds. Pushing respawn out by 2 seconds.
2014-12-12 13:47:27,842 ReportCrash[1914]: Saved crash report for fieryd[1955] version 0 to /Library/Logs/DiagnosticReports/fieryd_2014-12-12-134727_Foo-Bars-computer.crash
2014-12-12 13:47:30,348 com.apple.xpc.launchd[1]: (com.efi.fieryd[1963]) Service exited due to signal: Abort trap: 6
2014-12-12 13:47:30,349 com.apple.xpc.launchd[1]: (com.efi.fieryd) Service only ran for 0 seconds. Pushing respawn out by 2 seconds.
2014-12-12 13:47:30,362 ReportCrash[1914]: Saved crash report for fieryd[1963] version 0 to /Library/Logs/DiagnosticReports/fieryd_2014-12-12-134730_Foo-Bars-computer.crash

Greta_C
01-09-2015, 09:17 AM
I'll be sending you both a private message with a patch to try out in the next couple of days.

This should fix the daemon crash issue.
G.

abcdef
01-12-2015, 07:36 AM
Thanks Greta, that would be great. I'll check my forum notifications/messages in a day or two. It would be great timing, since I'm visiting the site where we have this trouble this friday (the 16th).

Will the patch be a regular installation package with the driver, just like the ones we already use, or should we apply it some other way?

sirspeedycranston
01-12-2015, 10:15 AM
Hey I am getting the same issue on 2 macs I have here at my shop.
is there anyway I can try out this patch as well?
thanks
-Tim

Greta_C
01-13-2015, 10:21 AM
Patch sent to both of you.

Let me know how you go.

We plan to release this patch publicly very soon.

ReluctantPrintAdmin
01-14-2015, 01:52 AM
Hi Greta, thanks for the patch, I'll post any problems I have with this.

JonNic
01-19-2015, 02:32 PM
Patch sent to both of you.

Let me know how you go.

We plan to release this patch publicly very soon.

Hi Greta

Im getting the same issue. Please could you send the patch or advise when it will be publicly available?

Thanks
Jon

abcdef
01-20-2015, 02:33 AM
Hi,

We have been trying the patch on a few machines now, and while the original error/crash is gone, another one has surfaced instead. Below are the logs. The error you see there happens over and over again, too.

Edit: I couldn't paste the log. This forum is annoying, it doesn't allow more than 10,000 characters in the posts. Raise that limit, please!

Instead I attach a file with the log.

Thanks.

1113

simon2000
01-20-2015, 03:04 AM
Hi. Thankfully I've found this forum.
Really causing problems for us here, 40 Macs. Need to move to 10.10.1 for Vectorworks issues, but this issue is stopping that. I can only get user's on 10.10.1 by removing any EFI software.
Do you have any approx. fix date so I can inform management please?

Simon.

favrj
01-20-2015, 10:41 AM
Hi Greta

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

Best regards

Greta_C
01-22-2015, 10:00 AM
Here's a link to a patch for you to try.
Just simply install it over the top.

https://www.dropbox.com/s/4qes3pkipvkd7ij/Fiery%20Printer%20Driver%2010.10%20patchJan9.dmg.z ip?dl=0

Let us know how it goes.

Greta.

abcdef
01-23-2015, 02:57 AM
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.

abcdef
01-26-2015, 02:28 AM
Any progress on this? The new errors/crashing is still going on, with a few seconds apart.

Greta_C
01-27-2015, 10:45 AM
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?

abordner
01-27-2015, 07:23 PM
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?



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::pGetServerValueFromD ict:::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

abcdef
01-28-2015, 03:59 AM
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/showthread.php/4855-OS-X-%2810.10.1%29-Fieryd-keeps-crashing-amp-reloading-constantly?p=16069#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!

Greta_C
01-28-2015, 08:16 AM
Sorry abcdef I didn't see your attached file before. We're looking into it now.
Apologies for the inconvenience.

Greta_C
01-29-2015, 12:36 AM
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.

abcdef
01-29-2015, 03:18 AM
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!

abordner
01-29-2015, 05:13 PM
I think that's correct, we're not seeing the crash and the process doesn't appear to be dying in Activity Monitor.

simon2000
01-30-2015, 07:46 AM
Hi, is there any release we can use? If so can you point us to the URL?

(Lots of iMacs here can't use the Fiery.)

Many thanks.

abcdef
01-30-2015, 11:17 AM
The case might very well be that the process isn't crashing anymore. But regardless, it or something relating to it is continously filling up our logs. Every time it happens a ton of lines are logged, and it happens with just a few seconds apart.

Please don't consider this case closed, we need the logging to be fixed as well. Thanks!

abcdef
02-03-2015, 04:44 PM
Hi, is there any progress on this since last week?

Greta_C
02-04-2015, 08:17 AM
Hi abcdef, please find some answers inline below in green.


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?

Sorry I meant is the print driver working normally now, with the exception of the messages in the log?

> 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?

See screenshot below showing the full properties button. Does this open as normal now, after the patch was applied?

1123

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 :)

Understand, we're still looking into the logging part.

Thanks!

simon2000
02-09-2015, 03:01 AM
Hi. Can anybody point me to a version of the software that we think may work for 10.10?

I am under great pressure to use the Xerox Fiery we purchased. I have had to start downgrading all Macs here to do this. Only to upgrade again when fixed.

Any advice or pointers really appreciated.

Thanks.

abcdef
02-09-2015, 07:53 AM
@simon2000 I assume that by now this is not a secret file or anything (seeing as everyone so far requesting it has gotten it), so here's the link to the patch to install atop the regular driver installation: https://www.dropbox.com/s/4qes3pkipvkd7ij/Fiery%20Printer%20Driver%2010.10%20patchJan9.dmg.z ip?dl=0

I'll try to get to the checking of information Greta requested ASAP.

simon2000
02-11-2015, 09:06 AM
I'll get on it now. Thanks again.

Simon.

Kevin Hayes
02-26-2015, 06:57 AM
I am having the same issue, I believe, with a Konica IC408 embedded.

When customer prints from OS 10.10 the fiery software crashes, but I can remote in and restart it no problem.

This is an older controller and has been replaced/swapped and is fully patched.

It software crashes right as the job prints, but does NOT happen if I connect direct and print from my mac running OS 10.8.5

Scott_W
02-26-2015, 10:11 AM
Not sure what you mean by "the fiery software crashes, but I can remote in and restart it no problem".

The Fiery itself crashes? And you remote into the Fiery itself via Remote Desktop to restart it?


Or do you mean Fiery app or driver on 10.10 Yosemite client crashes?

Kevin Hayes
02-26-2015, 11:39 AM
The actual Fiery software running on the server.

The Macs are running Ok after updating driver.

Scott_W
02-26-2015, 11:56 AM
Your issue does not seem related to what is being discussed on this thread.

On your Mac OS 10.10 machine, did you download the 10.10 IC-408 v2.0 print driver from EFi.com download site?

The release note for this driver available on download site has an important note about proper deletion of any older existing Fiery drivers to be done before new 10.10 driver is installed and IC-408 printer configured.

Did you follow those instructions?

1127

Kevin Hayes
02-26-2015, 12:05 PM
Did a double check to be sure, and yes.

Ran the uninstaller, it saw the old driver and removed it successfully.

Then I even ran it again to be sure.

Installed, driver seems to functioning as expected, but as soon as the file is printed I get the weird crash. Have tried PDFs, word and even email printing with same results, just varies on how many prints come out before the crash.

Scott_W
02-26-2015, 12:19 PM
You state "I can remote in and restart it no problem"...

When you first remote in after crash, does Fiery Bar at top of screen just "Processing" or "Exited"?


What type of printer do you select when configuring printer on the Yosemite? (IP, Bonjour, etc.)

Kevin Hayes
02-26-2015, 01:01 PM
It states "exited".

i have tried all, IPP and bonjour.

Scott_W
02-27-2015, 06:16 AM
I just downloaded the IC-408 Yosemite driver from EFI.com

I installed the uninstaller utility that comes with it (that we know is 10.10 compat.). I uninstalled all Fiery printers and drivers on my 10.10.2 iMac with utility (as if I was not sure they were fully 10.10 compat.)

I configured new printer (IP printer) using new driver.

I then printed successfully to my IC-408 from both Acrobat XI and InDesign CC2014
--------
I don't think this is a driver issue. Must be something with Fiery itself.

When was last time this Fiery was rebuilt?
Has it been fully patched (remote desktop to it and run System Updates)

I would suggest a fresh rebuild
Then enable Remote Desktop on it via Fiery Configure utility - then keep running System Updates until no more patches are left to install.

If by chance you get an error when first running System Updates, you will need to get patch 1-1CO771 from KM Support and run it from desktop of Fiery - then System Updates can be run.

Kevin Hayes
03-02-2015, 08:05 AM
Interesting, I did notice you are running 10.10.2, my customer is 10.10.1.

i actually replaced the whole controller with one not even taken out of the box yet.

Rebulit the system before going down with no issues, all patches and such loaded as expected with no issues.
this was after rebuilding and replacing hdd on original IC 408.

I am going to request my customer to update their system and see if this resolves.
Thanks you for that test, it was helpful indeed.

rick.goody
03-03-2015, 04:05 AM
I have a similar issue with canon imagePASS-A1 v1.01

We are running Yosemite 10.10.2 and logs are full of crash logs. Pretty much every 5 seconds

I have attached some of the logs to show you. From what I can tell printing is working fine, however it is very worrying this is happening. I have uninstalled the driver and re-installed via the latest download. We have around 50 Macs with this driver being used for the main Printer.

Greta_C
03-10-2015, 01:06 PM
For those seeing a FieryD crash, then you need the patch on our download site - marked as Mac OS X 10.10 Fiery Printer Driver patch. Install it on top of your 10.10 driver, and it will allow the driver to work normally, however you may notice some logging in the console logs about a 'gestalt selector'.

Please note - the logging is purely a cosmetic issue, the driver should be working fine, and it's not hurting your mac. However we understand it looks disturbing, and hence we'll release a new 10.10 patch in the near future, to replace the one online.

charles.betancourt
04-10-2015, 09:07 AM
We see it causing high utilization on many workstations. We use Ricoh MFP Copiers with Fiery Controllers, E-42B, E-22B and E-22C models. Is there a specific file in the framework that needs to be replaced across all of these models?

charles.betancourt
04-10-2015, 10:03 AM
Here is a crash report from a 10.9.5 workstation with only a Ricoh MP C5003 installed


4/10/15 11:36:58.067 AM ReportCrash[29477] com.apple.message.domain: com.apple.crashreporter.writereport.crash
com.apple.message.signature: fieryd
com.apple.message.signature2: UNBUNDLED ||| 0
com.apple.message.signature3: 0D92AADC44EDB8BE71A4DB5A396B815E
com.apple.message.result: NO
com.apple.message.summarize: YES
Sender_Mach_UUID: 3C9D65AC-CCF7-32B3-AE41-F8475197DE30
4/10/15 11:37:00.319 AM ReportCrash[29477] com.apple.message.domain: com.apple.crashreporter.writereport.crash
com.apple.message.signature: fieryd
com.apple.message.signature2: UNBUNDLED ||| 0
com.apple.message.signature3: 660676FD404B40916961CA393714FC68
com.apple.message.result: NO
com.apple.message.summarize: YES
Sender_Mach_UUID: 3C9D65AC-CCF7-32B3-AE41-F8475197DE30
4/10/15 11:37:02.567 AM ReportCrash[29477] com.apple.message.domain: com.apple.crashreporter.writereport.crash
com.apple.message.signature: fieryd
com.apple.message.signature2: UNBUNDLED ||| 0

charles.betancourt
04-21-2015, 04:16 PM
I've performed the steps outlines.
1. Removed all printers
2. Ran the uninstaller package
3. run the installer package
4. Add a Printer
5. Check the console for the fieryd crash message


Issue was not resolved

Bob_B
04-22-2015, 03:27 PM
It is not clear if you installed the patch that addresses the FieryD crash mentioned earlier in the thread. Please see the comment from Greta_C dated 3-10-2015 01:06 PM for the latest comments on the patch.

The patch is available on our download site at http://w3.efi.com/fiery/fiery-support/download/. After entering registration information, you will enter the Download Center. In the Application Software and Tools tab, select Fiery Driver in column 1 and then select Mac OS 10.10 Fiery Printer Driver patch v1.0 in column 2.

Bob_B
04-29-2015, 01:04 PM
An updated version of the Fiery Printer Driver patch for Mac OS 10.10 has been posted on the EFI driver download site at the same location that was mentioned above. The new patch replaces the earlier patch and addresses the log issues mentioned previously.

The new patch can be installed over and existing Mac OS 10.10 driver. It can also be installed over the previous version of the patch.

cwolsen
05-13-2015, 12:02 PM
Previous messages have referenced an OS patch to stop the constant crash and reload. Unfortunately the website has been updated and the links now 404. Can someone post an updated link please?

pwl_jim
05-13-2015, 03:23 PM
Please - can we get an updated link?

Thanks!

Garovski
05-14-2015, 06:35 AM
Please, anyone help with the link. ????

Bob_B
05-14-2015, 06:56 AM
The URL has changed after a redesign of our web site. To get to the download site, please go to http://www.efi.com/support-and-downloads/downloads/. Then, under Fiery Products, choose Fiery Drivers and Utilities.

cwolsen
05-15-2015, 06:24 AM
I followed your link, logged in (for the third time this morning) this takes me to the Download Center where I:
Select Partner (Ricoh) Select Printer (Afficio MP C6502) Select Fiery (Color Controller E-22B ver 1) Select Operating System (Mac OS)

The three choices I'm given are:
1. Release Notes dated 10/17/2014
2. Japanese Printer Drivers dated 10/17/2014
3. Multi-Language Printer Drivers dated 10/17/2014

I see no patch files nor updated drivers. What am I missing?

dave_hilltop
05-15-2015, 08:28 AM
Hello Greta_C! I have about four mac's that all have this issue as well. May I have this patch too? Attached is my crash report

5/14/15 3:06:50.230 PM ReportCrash[2696]: com.apple.message.domain: com.apple.crashreporter.writereport.crash
com.apple.message.signature: fieryd
com.apple.message.signature2: UNBUNDLED ||| ??? (0)
com.apple.message.signature3: 0DDB26253E0F79BC2073957E2EA510F7
com.apple.message.result: NO
com.apple.message.summarize: YES
SenderMachUUID: 963D36D1-19B7-33EC-972D-46604A25274C

cwolsen
05-15-2015, 11:44 AM
After repeated attempts the link just worked for me, whomever is responsible, thank you. This fixed the constant crash in the console system messages.

http://www.efi.com/support-and-downl...l=394~v1.1&os=

RobertHammen
05-29-2015, 09:27 AM
Link is now missing since the website redesign. Have clicked on numerous different Fiery RIPs, OS X 10.6-10.10, show drivers, and cannot get the download to be displayed.

Where is this file? Please!

Scott_W
05-29-2015, 09:35 AM
You are in Download Center, but you need to click on "Application Software and Tools" tab instead of "Printer Drivers"

Then click on "Fiery Driver" on left column. On right you should then see Driver Patch v1.1

Greta_C
05-29-2015, 09:48 AM
The patch is there, but not listed under the product drivers section.

At the top there's a tab that says 'Application Software and Tools'. Click on this, then select Fiery driver from the list, and the 10.10 patch is there. See the screenshot below.
I just downloaded it again to be sure.

1188

Let me know if still any issues,

rdoray
06-23-2015, 07:40 AM
Same Problem with my IMac.. Constant Errors in Console.. Every 3 seconds. Occasionally, network crashes because of this. Can I get a fix too? Even if it is BETA?

thanks
rob


I'll be sending you both a private message with a patch to try out in the next couple of days.

This should fix the daemon crash issue.
G.