This error appears every 31 seconds: [17:52:01 WARNING papyon.msnp2p.transport] TLPv1 Parse Error: empty chunk for non-empty blob 00 00 00 00 90 93 05 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 04 00 00 00 bb 2e 05 01 00 00 00 00 00 00 00 00 00 00 00 00 [17:52:01 WARNING papyon.msnp2p.transport] TLPv1 Parse Error: empty chunk for non-empty blob 00 00 00 00 8f 93 05 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 04 00 00 00 bb 2e 05 01 00 00 00 00 00 00 00 00 00 00 00 00 [17:52:01 ERROR papyon.msnp2p.transport] Trying to append a chunk to the wrong blob Traceback (most recent call last): File "/home/sven/emesene/emesene/e3/papylib/papyon/papyon/msnp2p/transport/transport_manager.py", line 168, in _on_chunk_received blob.append_chunk(chunk) File "/home/sven/emesene/emesene/e3/papylib/papyon/papyon/msnp2p/transport/TLP.py", line 145, in append_chunk assert self.id == chunk.blob_id, "Trying to append a chunk to the wrong blob" AssertionError: Trying to append a chunk to the wrong blob [17:52:01 WARNING papyon.msnp2p.transport] Couldn't append chunk to blob, ignoring it [17:52:02 ERROR papyon.msnp2p.transport] Trying to append a chunk to the wrong blob Traceback (most recent call last): File "/home/sven/emesene/emesene/e3/papylib/papyon/papyon/msnp2p/transport/transport_manager.py", line 168, in _on_chunk_received blob.append_chunk(chunk) File "/home/sven/emesene/emesene/e3/papylib/papyon/papyon/msnp2p/transport/TLP.py", line 145, in append_chunk assert self.id == chunk.blob_id, "Trying to append a chunk to the wrong blob" AssertionError: Trying to append a chunk to the wrong blob [17:52:02 WARNING papyon.msnp2p.transport] Couldn't append chunk to blob, ignoring it I'm not sure why, and not sure if I can reproduce it either. I didn't have the highest level of debug enabled, so there's no way for me to get a more complete log unless I'm able to reproduce this.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.