[Bug]: Linux native meshtasticd SEGV

[brauhausdc]

Category

Other

Hardware

Linux Native

Is this bug report about any UI component firmware like InkHUD or Meshtatic UI (MUI)?

• Meshtastic UI aka MUI colorTFT
• InkHUD ePaper
• OLED slide UI on any display

Firmware Version

2.6.11.25

Description

Linux Native meshtasticd has been segv’ing when I try to start it since installing 2.6.11.25:

hostname:~$ sudo systemctl status meshtasticd

• meshtasticd.service - Meshtastic Native Daemon
  Loaded: loaded (/lib/systemd/system/meshtasticd.service; enabled; preset: enabled)
  Active: activating (auto-restart) (Result: signal) since Sat 2025-07-19 11:57:36 GMT; 2s ago
  Process: 26676 ExecStart=/usr/bin/meshtasticd (code=killed, signal=SEGV)
  Main PID: 26676 (code=killed, signal=SEGV)
  CPU: 114ms

hostname:$ apt list --installed mesh*
Listing... Done
meshtasticd/unknown,now 2.6.11.25obs60ec05e~beta armhf [installed]

Using a MeshAdv board on a Pi-2b 1.1 with a Reasonably current version of RaspPi OS. Worked fine before.

Relevant log output

[mverch67]

What happens if you run manually /usr/bin/meshtasticd in a terminal window? Post the output under Relevant log output above.

[brauhausdc]

malloc/free issue maybe? ***@***.***:~$ sudo /usr/bin/meshtasticd Portduino is starting, VFS root at /root/.portduino/default Set up Meshtastic on Portduino... free(): invalid pointer Aborted Or as root: ***@***.***:~# sudo /usr/bin/meshtasticd Portduino is starting, VFS root at /root/.portduino/default Set up Meshtastic on Portduino... Segmentation fault Trying it with gdb (but mostly failing, since it wasn’t compiled with debugging symbols) ***@***.***:~# gdb /usr/bin/meshtasticd GNU gdb (Raspbian 13.1-3) 13.1 Copyright (C) 2023 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "arm-linux-gnueabihf". Type "show configuration" for configuration details. For bug reporting instructions, please see: <https://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/bin/meshtasticd... (No debugging symbols found in /usr/bin/meshtasticd) (gdb) run Starting program: /usr/bin/meshtasticd [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1". Portduino is starting, VFS root at /root/.portduino/default Set up Meshtastic on Portduino... Program received signal SIGSEGV, Segmentation fault. 0x0046916e in ?? ()

…

On Jul 19, 2025, at 10:52 AM, Manuel ***@***.***> wrote: mverch67 left a comment (meshtastic/firmware#7384) What happens if you run manually /usr/bin/meshtasticd in a terminal window? Post the output under Relevant log output above. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[mverch67]

Program received signal SIGSEGV, Segmentation fault.
0x0046916e in ?? ()

you forgot to type where or bt to see the full stacktrace.