Hi Antoine! Thank you for filing this bug, especially because I hadn't yet had the chance to verify successful migration to trixie.
P.S. I'm delighted to hear that you're using this software! I've been unsuccessfully advocating for an initial setup wizard to make it easy for new users to set up a working Syncthing cluster, and I'd appreciate it if you (and/or others) could add a comment here: https://github.com/Martchus/syncthingtray/issues/134 Reply follows inline: On Wed, 26 Mar 2025 15:21:49 -0400 Antoine Beaupre <anar...@debian.org> wrote: > Package: syncthingtray > Version: 1.5.4-1 > Severity: grave > > Hi! > > Syncthingtray doesn't start anymore on trixie: > > anarcat@angela:~> syncthingtray > Info: Single instance application ID: Syncthing Tray-Martchus-1000 > terminate called after throwing an instance of 'std::bad_alloc' > what(): std::bad_alloc > fish: Job 1, 'syncthingtray' terminated by signal SIGABRT (Abort) > > I'm not sure what's going on, it used to work fine. I suspect part of > the issue might be the package's failure to migrate from unstable, as > installing the package from unstable works fine. Yup it's something like that :) This horribly opaque crash occurs because syncthingtray needs to migrate in lock-step with its martchus-* dependencies. Tldr, qt5-to-qt6 migration, qt6-webengine-dev doesn't support mips64el, thus syncthingtray has unsatisfied deps and ftbfs, thus I've filled a RM bug that blocks the resolution of this one you filed. Also, thanks for your resourcefulness in finding and documenting an immediate solution for everyone else who now has a broken Syncthing Tray. 'hope to see you this year! Nicholas
signature.asc
Description: PGP signature
