Hi Bernhard, Well that explains that then, I didn't change anything to pin to the patched version. In that case it was fixed and I broke it. Hopefully the patch will be part of a future release and it'll be peachy again. Thanks for explaining what happened.
-- Tim McConnell <tmcconnell...@gmail.com> On Fri, 2023-03-24 at 11:52 +0100, Bernhard Übelacker wrote: > Am 23.03.23 um 17:38 schrieb Tim McConnell: > > Bernhard, > > Just cause I said it was fixed this happens to show up in > > journalctl: > > systemd-coredump[3614]: Process 1704 (pads) of user 0 dumped core. > > > > Module > > libsystemd.so.0 from deb systemd-252.5-2.amd64 > > Stack trace of > > thread 1704: > > #0 > > 0x00005600f24f6954 print_arp_asset_screen (pads + 0x9954) > > #1 > > 0x00005600f24f66f0 print_arp_asset (pads + 0x96f0) > > #2 > > 0x00007fdc7fdb54f6 n/a (libpcap.so.0.8 + 0x84f6) > > #3 > > 0x00007fdc7fdb58ec n/a (libpcap.so.0.8 + 0x88ec) > > #4 > > 0x00007fdc7fdbcd1d pcap_loop (libpcap.so.0.8 + 0xfd1d) > > #5 > > 0x00005600f24efe5b main_pads (pads + 0x2e5b) > > #6 > > 0x00005600f24ef47b main (pads + 0x247b) > > #7 > > 0x00007fdc7fbec18a __libc_start_call_main (libc.so.6 + 0x2718a) > > #8 > > 0x00007fdc7fbec245 __libc_start_main_impl (libc.so.6 + 0x27245) > > #9 > > 0x00005600f24ef4b1 _start (pads + 0x24b1) > > ELF object > > binary > > architecture: AMD x86-64 > > Mar 04 14:31:02 DebianTim systemd[1]: > > systemd-coredump@0-3613-0.service: Deactivated successfully. > > > > Well I thought it was fixed :-( > > > Hello Time, > are you sure that your rebuilt package is still in place? > The offsets in your new backtrace are exactly the same as > in the email from 8 Feb 2023. > > We have not changed the version of the rebuilt package. > Additionally built with "-b". > Then with a "apt dist-upgrade" always > the Debian version gets reinstalled. > > Sorry for not mentioning that extra care has to be taken > to hold the rebuilt package version in place. > > Kind regards, > Bernhard