The only thing we can tell from this stack trace is that an assertion happened somewhere further down in the stack, which is not visible in this stack trace.
If the reporter can try to reproduce the issue with netatalk 2.2.9 or later and share the complete stack trace again if the crash occurs, we can look further into the cause.
The only thing we can tell from this stack trace is that an assertion happened somewhere further down in the stack, which is not visible in this stack trace.
If the reporter can try to reproduce the issue with netatalk 2.2.9 or later and share the complete stack trace again if the crash occurs, we can look further into the cause.