Upon the initial sync, I found the following error messages in the log: … 2026-04-07 18:38:35.491 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1618 Synced 3647399/3647400 (99%, 1 left) 2026-04-07 18:38:35.992 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1618 Synced 3647400/3647400 2026-04-07 18:38:36.458 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:2409 Synced 11449 blocks in 5.5 hours (0.58 blocks per second) 2026-04-07 18:38:36.458 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:2413 2026-04-07 18:38:36.458 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:2413 ********************************************************************** 2026-04-07 18:38:36.458 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:2413 You are now synchronized with the network. You may now start monero-wallet-cli. 2026-04-07 18:38:36.458 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:2413 2026-04-07 18:38:36.458 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:2413 Use the "help" command to see the list of available commands. 2026-04-07 18:38:36.458 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:2413 ********************************************************************** 2026-04-07 18:38:39.493 [P2P9] ERROR net.p2p.tx src/cryptonote_protocol/levin_notify.cpp:575 Unable to send transaction(s) via Dandelion++ stem The level is ERROR, so probably at least a decrease in privacy is to worry about. Here is my ~/.config/systemd/user/monerod.service: [Unit] Description=Monero Node After=network.target [Service] Type=simple ExecStart=/usr/bin/monerod --data-dir /path_to_my_Monero_folder --prune-blockchain --log-file /path_to_my_Monero_folder/bitmonero.log --non-interactive Restart=always RestartSec=30 Environment=MONERO_RANDOMX_UMASK=1 Nice=19 IOSchedulingClass=idle [Install] WantedBy=default.target I'd be grateful for a fix. Albert
This could fix the error. Can you please test this?
Dear Bastian, Thank you for the patch! For an unknown reason, I didn't get an e-mail corresponding to your message #10. I checked bugs.debian.org/1132940 out of curiosity manually today and saw your message only now. Today, I upgraded the package to 0.18.5.0+~0+20260428-1, and the error did not occur today yet. The last four such errors happened before the upgrade and quite rarely: 2026-04-26 08:59:10.073 [P2P0] ERROR net.p2p.tx src/cryptonote_protocol/levin_notify.cpp:575 Unable to send transaction(s) via Dandelion++ stem 2026-04-28 05:12:02.797 [P2P8] ERROR net.p2p.tx src/cryptonote_protocol/levin_notify.cpp:575 Unable to send transaction(s) via Dandelion++ stem 2026-06-15 11:44:15.028 [P2P6] ERROR net.p2p.tx src/cryptonote_protocol/levin_notify.cpp:575 Unable to send transaction(s) via Dandelion++ stem 2026-06-19 10:02:41.344 [P2P3] ERROR net.p2p.tx src/cryptonote_protocol/levin_notify.cpp:575 Unable to send transaction(s) via Dandelion++ stem I checked out the code and applied your patch locally, but now I start running into all kinds of issues during build. For example, though I have cmake 3.31.6, `make` outputs pages of warnings, the earliest of which is this: CMake Deprecation Warning at external/randomx/CMakeLists.txt:29 (cmake_minimum_required): Compatibility with CMake < 3.10 will be removed from a future version of CMake. Update the VERSION argument value. Or, use the ... syntax to tell CMake that the project requires at least but has been updated to work with policies introduced by or earlier. My machine does not have a development environment suitable for proper code development, and I don't have any insight into the warnings. So even if the compilation ever succeeds (it takes long), and even if I succeed to start the compiled monerod, I'm unsure how useful my feedback would be; my apologies. Probably unrelated, but still better to mention this. Upon issuing `systemctl --user restart monerod` or `systemctl --user stop monerod` (with monerod from the Debian package 0.18.5.0+~0+20260428-1), I get this into the log: 2026-06-20 22:17:56.483 [SRV_MAIN] INFO global src/daemon/p2p.h:81 p2p net loop stopped 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:134 Exception: std::system_error 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:135 Unwound call stack: 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:173 [1] 0xab) [0x555dede82aa6]:__cxa_throw+0xab) [0x555dede82aa6] 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:173 [2] /usr/bin/monerod(+0xbd701) [0x555dede7d701] 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:173 [3] /usr/bin/monerod(+0x73bfa9) [0x555dee4fbfa9] 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:173 [4] 0xbc97) [0x7f54092ebc97]:_64-linux-gnu/libboost_thread.so.1.90.0(+0xbc97) [0x7f54092ebc97] 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:173 [5] 0x92b7b) [0x7f540869eb7b]:_64-linux-gnu/libc.so.6(+0x92b7b) [0x7f540869eb7b] 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:173 [6] 0x1107f8) [0x7f540871c7f8]:_64-linux-gnu/libc.so.6(+0x1107f8) [0x7f540871c7f8] 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:173 A stacktrace is probably not something we should expect during normal operation, should we? As a rule of thumb, an exit should be graceful; upon exit, a program should free its resources itself properly. Gratefully, Albert
Dear Bastian, Thank you for the patch! For an unknown reason, I didn't get an e-mail corresponding to your message #10. I checked bugs.debian.org/1132940 out of curiosity manually today and saw your message only now. Today, I upgraded the package to 0.18.5.0+~0+20260428-1, and the error did not occur today yet. The last four such errors happened before the upgrade and quite rarely: 2026-04-26 08:59:10.073 [P2P0] ERROR net.p2p.tx src/cryptonote_protocol/levin_notify.cpp:575 Unable to send transaction(s) via Dandelion++ stem 2026-04-28 05:12:02.797 [P2P8] ERROR net.p2p.tx src/cryptonote_protocol/levin_notify.cpp:575 Unable to send transaction(s) via Dandelion++ stem 2026-06-15 11:44:15.028 [P2P6] ERROR net.p2p.tx src/cryptonote_protocol/levin_notify.cpp:575 Unable to send transaction(s) via Dandelion++ stem 2026-06-19 10:02:41.344 [P2P3] ERROR net.p2p.tx src/cryptonote_protocol/levin_notify.cpp:575 Unable to send transaction(s) via Dandelion++ stem I checked out the code and applied your patch locally, but now I start running into all kinds of issues during build. For example, though I have cmake 3.31.6, `make` outputs pages of warnings, the earliest of which is this: CMake Deprecation Warning at external/randomx/CMakeLists.txt:29 (cmake_minimum_required): Compatibility with CMake < 3.10 will be removed from a future version of CMake. Update the VERSION argument <min> value. Or, use the <min>...<max> syntax to tell CMake that the project requires at least <min> but has been updated to work with policies introduced by <max> or earlier. My machine does not have a development environment suitable for proper code development, and I don't have any insight into the warnings. So even if the compilation ever succeeds (it takes long), and even if I succeed to start the compiled monerod, I'm unsure how useful my feedback would be; my apologies. Probably unrelated, but still better to mention this. Upon issuing `systemctl --user restart monerod` or `systemctl --user stop monerod` (with monerod from the Debian package 0.18.5.0+~0+20260428-1), I get this into the log: 2026-06-20 22:17:56.483 [SRV_MAIN] INFO global src/daemon/p2p.h:81 p2p net loop stopped 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:134 Exception: std::system_error 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:135 Unwound call stack: 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:173 [1] 0xab) [0x555dede82aa6]:__cxa_throw+0xab) [0x555dede82aa6] 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:173 [2] /usr/bin/monerod(+0xbd701) [0x555dede7d701] 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:173 [3] /usr/bin/monerod(+0x73bfa9) [0x555dee4fbfa9] 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:173 [4] 0xbc97) [0x7f54092ebc97]:_64-linux-gnu/libboost_thread.so.1.90.0(+0xbc97) [0x7f54092ebc97] 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:173 [5] 0x92b7b) [0x7f540869eb7b]:_64-linux-gnu/libc.so.6(+0x92b7b) [0x7f540869eb7b] 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:173 [6] 0x1107f8) [0x7f540871c7f8]:_64-linux-gnu/libc.so.6(+0x1107f8) [0x7f540871c7f8] 2026-06-20 22:17:56.492 7f37852f96c0 INFO stacktrace src/common/stack_trace.cpp:173 A stacktrace is probably not something we should expect during normal operation, should we? As a rule of thumb, an exit should be graceful; upon exit, a program should free its resources itself properly. Gratefully, Albert
Several hours later, after tons of warnings, the build finished successfully. I started the just compiled monerod, and, so far, no error message of the type “ERROR net.p2p.tx src/cryptonote_protocol/levin_notify.cpp:575 Unable to send transaction(s) via Dandelion++ stem” has occurred.
Oh. The version I checked out using the public https://github.com/monero-project/monero.git (obtained from https://github.com/monero-project/monero , click on the green “Code“ ) turned to be 0.18.1 (according to /tmp/monero/bin/monerod --version), which is behind Debian's 0.18.5 (according to monerod --version). Why is the upstream version lower than the downstream one?! Anyway, forget my tests yesterday and today, as I apparently wasted lots of time for nothing.
And the new attempt with a new checkout (`git clone --recursive https://github.com/monero-project/monero https://github.com/monero-project/monero ` followed by `cd monero`, `git checkout release-v0.18`, and `make`) yielded a couple of warnings followed by an error CMake Error at /usr/share/cmake-3.31/Modules/FindPackageHandleStandardArgs.cmake:233 (message): Could NOT find Boost (missing: locale) (found suitable version "1.83.0", minimum required is "1.62") Call Stack (most recent call first): /usr/share/cmake-3.31/Modules/FindPackageHandleStandardArgs.cmake:603 (_FPHSA_FAILURE_MESSAGE) /usr/share/cmake-3.31/Modules/FindBoost.cmake:2423 (find_package_handle_standard_args) CMakeLists.txt:1108 (find_package) I ran out of free AI-chatbot queries to ask how to proceed from here, so this is clearly above my level. I kindly ask for understanding that I won't be able to perform more development-level tests.
Please install the experimental version 0.18.5.0+~0+20260428-2~exp which includes the patch.
We believe that the bug you reported is fixed in the latest version of monero, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1132940@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann <bage@debian.org> (supplier of updated monero package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@ftp-master.debian.org) Format: 1.8 Date: Mon, 22 Jun 2026 01:02:34 +0200 Source: monero Architecture: source Version: 0.18.5.0+~0+20260428-2~exp Distribution: experimental Urgency: medium Maintainer: Debian Cryptocoin Team <team+cryptocoin@tracker.debian.org> Changed-By: Bastian Germann <bage@debian.org> Closes: 1132940 Changes: monero (0.18.5.0+~0+20260428-2~exp) experimental; urgency=medium . * Fall back to unfiltered outgoing peers (Closes: #1132940) Checksums-Sha1: 02615acbc12e9172f7793ee438a1042b2a0481eb 2793 monero_0.18.5.0+~0+20260428-2~exp.dsc abec0e79e9d8b640258fb9569fa58dbf6d47c3d9 19824 monero_0.18.5.0+~0+20260428-2~exp.debian.tar.xz dca34843e72dae86f6084b299947dda84b70bfd8 10493 monero_0.18.5.0+~0+20260428-2~exp_source.buildinfo Checksums-Sha256: 1ddf65aa2dadab72c07c87ba63f203708be612918509087eb47feb9649135eec 2793 monero_0.18.5.0+~0+20260428-2~exp.dsc 9d3b0652123245b83b7e4e635eb1e767557fb2b37852619d8e81e01dbbc8edd3 19824 monero_0.18.5.0+~0+20260428-2~exp.debian.tar.xz 7c3aa7be3aba29f7e2772feb681fc8375b6c266708f21fe421709106392d460e 10493 monero_0.18.5.0+~0+20260428-2~exp_source.buildinfo Files: 19b8e348bfbd20528065a11122f9a38a 2793 utils optional monero_0.18.5.0+~0+20260428-2~exp.dsc a58c0db17ad4100b33fc4848093064fd 19824 utils optional monero_0.18.5.0+~0+20260428-2~exp.debian.tar.xz 04194674f4fffe2d9c6d4e5213d6e0e4 10493 utils optional monero_0.18.5.0+~0+20260428-2~exp_source.buildinfo -----BEGIN PGP SIGNATURE----- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmo4bb4QHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFKuODADErfgb1fJ7YuKoUE9n7qGPWGHUasaRs70a CSkia/b6JuCz5+4AYHhigGreFcYaKrL9iuhnioZ4OQXn5BH0GkVLMV0M0snWBs3q ExPVl3bsDOgxMI+eOcmkVFkBKlLDLZNlejNenlIFLbFmyg9mjVGynBfMQVTDpsCs 7iBR2pgHGMQwJoLQIisf0yISQI8j6AqiDYX/B8yGJXBTmJ2S1zOcEH7aeLRqz3+N wgWzNaBP5iivXMacI2KdtzNKHo5q56oVmpdPONhivq8MXELsQSlYmn8U+u5ajwPG hlDZ54Xax/+y34AOtlUzvHeAaegt1rizpVOl/5sI7mqFa6QHBaw27ZCfSMsWtVty 8hwJvSipZ6Udi3vWBE0lfzt7IPLnkFaSD6obOvNJHBJ9pEBcHYShWsvw4PJ8YWnX SoAzp+NbfJ16vhS8KjjgjZrcYk4KMBo+PKUYNzWzwrh24Def6JgJAljT5HjmGuyn rNoTCvt44utN3G0Ca5GcGMU5PWOjT/M= =+vnO -----END PGP SIGNATURE-----