Hi,
On Tue, Aug 18, 2026 at 10:34:11AM +0200, darkdragon via 
Debian-on-mobile-maintainers wrote:
> Please find the related coredump attached below:
> 
>            PID: 21642 (eg25-manager)
>            TID: 21642 (eg25-manager)
>            UID: 0 (root)
>            GID: 0 (root)
>         Signal: 11 (SEGV)
>      Timestamp: Tue 2026-08-18 10:29:37 CEST (1min 58s ago)
>   Command Line: /usr/bin/eg25-manager
>     Executable: /usr/bin/eg25-manager
>  Control Group: /system.slice/eg25-manager.service
>           Unit: eg25-manager.service
>          Slice: system.slice
>        Boot ID: 7af4c1ddee46457d8d4dc22dffffeff6
>     Machine ID: 49825574758b4acba5291059395d96fe
>       Hostname: mobian
>        Storage:
> /var/lib/systemd/coredump/core.eg25-manager.0.7af4c1ddee46457d8d4dc22dffffeff6.21642.1787041777000000.zst
> (present)
>   Size on Disk: 350.7K
>        Message: Process 21642 (eg25-manager) of user 0 dumped core.
> 
>                 Module libblkid.so.1 from deb util-linux-2.42.2-2.arm64
>                 Module libzstd.so.1 from deb libzstd-1.5.7+dfsg-4.arm64
>                 Module libmount.so.1 from deb util-linux-2.42.2-2.arm64
>                 Stack trace of thread 21642:
>                 #0  0x0000005572d171f8 n/a (eg25-manager + 0x71f8)
>                 #1  0x0000005572d1fad0 n/a (eg25-manager + 0xfad0)
>                 #2  0x0000005572d1fe54 n/a (eg25-manager + 0xfe54)
>                 #3  0x0000007f87f48d5c n/a (libgio-2.0.so.0 + 0xc8d5c)
>                 #4  0x0000007f87f48da0 n/a (libgio-2.0.so.0 + 0xc8da0)
>                 #5  0x0000007f8810ad58 n/a (libglib-2.0.so.0 + 0x5ad58)
>                 #6  0x0000007f8810e304 n/a (libglib-2.0.so.0 + 0x5e304)
>                 #7  0x0000007f8810eeac g_main_loop_run
> (libglib-2.0.so.0 + 0x5eeac)
>                 #8  0x0000005572d162c4 n/a (eg25-manager + 0x62c4)
>                 #9  0x0000007f8794251c n/a (libc.so.6 + 0x2251c)
>                 #10 0x0000007f879425fc __libc_start_main (libc.so.6 + 0x225fc)
>                 #11 0x0000005572d16430 n/a (eg25-manager + 0x6430)
> 
>                 Stack trace of thread 21645:
>                 #0  0x0000007f87a0ff64 syscall (libc.so.6 + 0xeff64)
>                 #1  0x0000007f88140fdc g_cond_wait_until
> (libglib-2.0.so.0 + 0x90fdc)
>                 #2  0x0000007f880d5394 n/a (libglib-2.0.so.0 + 0x25394)
>                 #3  0x0000007f88141b78 n/a (libglib-2.0.so.0 + 0x91b78)
>                 #4  0x0000007f881412c8 n/a (libglib-2.0.so.0 + 0x912c8)
>                 #5  0x0000007f879a8ff4 n/a (libc.so.6 + 0x88ff4)
>                 #6  0x0000007f87a1231c n/a (libc.so.6 + 0xf231c)
> 
>                 Stack trace of thread 21647:
>                 #0  0x0000007f87a0ff64 syscall (libc.so.6 + 0xeff64)
>                 #1  0x0000007f88140fdc g_cond_wait_until
> (libglib-2.0.so.0 + 0x90fdc)
>                 #2  0x0000007f880d5394 n/a (libglib-2.0.so.0 + 0x25394)
>                 #3  0x0000007f88141b78 n/a (libglib-2.0.so.0 + 0x91b78)
>                 #4  0x0000007f881412c8 n/a (libglib-2.0.so.0 + 0x912c8)
>                 #5  0x0000007f879a8ff4 n/a (libc.so.6 + 0x88ff4)
>                 #6  0x0000007f87a1231c n/a (libc.so.6 + 0xf231c)
> 
>                 Stack trace of thread 21643:
>                 #0  0x0000007f87a0ff64 syscall (libc.so.6 + 0xeff64)
>                 #1  0x0000007f88140a34 g_cond_wait (libglib-2.0.so.0 + 
> 0x90a34)
>                 #2  0x0000007f880d53cc n/a (libglib-2.0.so.0 + 0x253cc)
>                 #3  0x0000007f881415dc n/a (libglib-2.0.so.0 + 0x915dc)
>                 #4  0x0000007f881412c8 n/a (libglib-2.0.so.0 + 0x912c8)
>                 #5  0x0000007f879a8ff4 n/a (libc.so.6 + 0x88ff4)
>                 #6  0x0000007f87a1231c n/a (libc.so.6 + 0xf231c)
> 
>                 Stack trace of thread 21644:
>                 #0  0x0000007f879b2628 n/a (libc.so.6 + 0x92628)
>                 #1  0x0000007f879a563c n/a (libc.so.6 + 0x8563c)
>                 #2  0x0000007f879a5690 n/a (libc.so.6 + 0x85690)
>                 #3  0x0000007f87a07ccc ppoll (libc.so.6 + 0xe7ccc)
>                 #4  0x0000007f8810e37c n/a (libglib-2.0.so.0 + 0x5e37c)
>                 #5  0x0000007f8810eb88 g_main_context_iteration
> (libglib-2.0.so.0 + 0x5eb88)
>                 #6  0x0000007f8810ebf0 n/a (libglib-2.0.so.0 + 0x5ebf0)
>                 #7  0x0000007f881412c8 n/a (libglib-2.0.so.0 + 0x912c8)
>                 #8  0x0000007f879a8ff4 n/a (libc.so.6 + 0x88ff4)
>                 #9  0x0000007f87a1231c n/a (libc.so.6 + 0xf231c)
> 
>                 Stack trace of thread 21648:
>                 #0  0x0000007f879b2628 n/a (libc.so.6 + 0x92628)
>                 #1  0x0000007f879a563c n/a (libc.so.6 + 0x8563c)
>                 #2  0x0000007f879a5690 n/a (libc.so.6 + 0x85690)
>                 #3  0x0000007f87a07ccc ppoll (libc.so.6 + 0xe7ccc)
>                 #4  0x0000007f8810e37c n/a (libglib-2.0.so.0 + 0x5e37c)
>                 #5  0x0000007f8810eeac g_main_loop_run
> (libglib-2.0.so.0 + 0x5eeac)
>                 #6  0x0000007f87fc24d4 n/a (libgio-2.0.so.0 + 0x1424d4)
>                 #7  0x0000007f881412c8 n/a (libglib-2.0.so.0 + 0x912c8)
>                 #8  0x0000007f879a8ff4 n/a (libc.so.6 + 0x88ff4)
>                 #9  0x0000007f87a1231c n/a (libc.so.6 + 0xf231c)
> 
>                 Stack trace of thread 21646:
>                 #0  0x0000007f87a0ff64 syscall (libc.so.6 + 0xeff64)
>                 #1  0x0000007f88140fdc g_cond_wait_until
> (libglib-2.0.so.0 + 0x90fdc)
>                 #2  0x0000007f880d5394 n/a (libglib-2.0.so.0 + 0x25394)
>                 #3  0x0000007f88141b78 n/a (libglib-2.0.so.0 + 0x91b78)
>                 #4  0x0000007f881412c8 n/a (libglib-2.0.so.0 + 0x912c8)
>                 #5  0x0000007f879a8ff4 n/a (libc.so.6 + 0x88ff4)
>                 #6  0x0000007f87a1231c n/a (libc.so.6 + 0xf231c)
>                 ELF object binary architecture: AARCH64

I'm not a eg24-manager maintainer but just as a general note:

- without debug symbols those are often pretty useless. Debian has dbgsym 
packages
  of eg25-manager and debuginfod so two solutions exist to fetch those.
- I'd grab the backtrace via gdb after installing those. There's no need
  to trigger the crash again since the symbols can be appplied to
  existing coredumps just fine.
  
Cheers,
 -- Guido

Reply via email to