Ross Patterson

I was seeing this regularly before, and I haven't seen this in some time, so I suspect it's been resolved by the above releases, though I don't have any technical...

While looking for any existing issues or other context for this error message, I found #2727 which mentions the same assertion, but that thread is quite long and most of...

> After having seen rpatterson's "fix" of adding the config directory That wasn't intended to describe a fix, rather to describe how I reproduced the issue. IOW, running `$ transmission-daemon...

> I'm experiencing this too ever since 4.0 got released, same linuxserver/transmission docker implementation Oh, in case it helps, [this is how I'm keeping the image at v3.0](https://gitlab.com/rpatterson/prunerr/-/commit/7af8d989492435371ff2672cfc4de11735fa2557#35b8c13cf2eb2a194eada000eb310d65aed53b2a_9_9) until this...

> For one thing I don't understand why these builds are being made with assertions enabled FYI, this is the "official" image in the sense that it's the one linked...

> Those shouldn't make it into production code; they're only meant for test builds. To clarify, I assume this doesn't mean this issue will be resolved by disabling assertions, @ckerr?

> it is Can you clarify, @nekopsykose? Is that in reference to [my previous comment](https://github.com/transmission/transmission/issues/4878#issuecomment-1431380221)?

[I no longer see the assertion errors running the latest Docker image](https://github.com/linuxserver/docker-transmission/issues/232#issuecomment-1431512728), but I'm still unclear if that's just hiding a real underlying issue.

> related: https://retrace.fedoraproject.org/faf/problems/bthash/?bth=b350cbeb1debd5b1654f68c2a1320c098d74a8e3&bth=8b70bd742b7839089fa8399e5db24e001ca248cb&bth=f583ff12c77a28a072a6a7d784c33361d63cc853 How is that related? It's not obvious from looking at that link.

It seems like there may be a real issue underlying this somewhere, but what I encountered is long since resolved.