mirror of
https://github.com/Drop-OSS/packages.git
synced 2026-07-22 08:35:26 -04:00
[GH-ISSUE #1] [BUG] libayatana is a lazy dependency instead of a linked one #3
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Beethoven-n on GitHub (Aug 8, 2025).
Original GitHub issue: https://github.com/Drop-OSS/packages/issues/1
this is getting in the way of making a tauri-independent appimage, @quexeky could you look at this?
https://github.com/Drop-OSS/drop-app/pull/103/#issuecomment-3161699871
@quexeky commented on GitHub (Aug 8, 2025):
I'm thinking that the solution is probably something in the build script. I haven't looked much into it, but I believe that there are a few ways to force packaging libraries into the actual binary
@quexeky commented on GitHub (Aug 8, 2025):
The only way that I've found to do it is by actually including it in the appimage files: https://v2.tauri.app/distribute/appimage/#custom-files
@Beethoven-n commented on GitHub (Aug 8, 2025):
so when is it actually used? how does the lazy part work, and what would happen if you were to actually import it instead?
@quexeky commented on GitHub (Aug 8, 2025):
The problem is that we don't do that - it's done through libappindicator, which itself is referenced by tauri's System Tray, so unless we want to rewrite that, it's only ever loaded at runtime instead of at compile time. The Lazy part is that "load at runtime" part
@Beethoven-n commented on GitHub (Aug 11, 2025):
i think the more pressing issue is this kind of breaks the aur package. maybe i should close this and put it in the new packages repo?
@quexeky commented on GitHub (Aug 11, 2025):
Don't mind me forgetting that I can transfer issues here lmao. But yeah that's a good point that we need to update the dependencies for the aur package
@Beethoven-n commented on GitHub (Aug 11, 2025):
i would say it should probably be done in a way that Kind of links to it explicitly, at least technically, just so that
lddorreadelfcan see that it's a dependency so my appimage PR can work, but i think that's probably why paru refuses to install it when you naively add the library to the depends array@DecDuck commented on GitHub (Aug 12, 2025):
I got it to link:
Using the
appindicator3-syspackage, and then just calling the simplest function in lib.rs like this:@Beethoven-n commented on GitHub (Aug 12, 2025):
that'll do it lmao
is that in main already?
@DecDuck commented on GitHub (Aug 12, 2025):
Just added to your AppImage PR.
@Beethoven-n commented on GitHub (Aug 12, 2025):
gonna test the build to see if it runs, and then if it uses all the correct libs
thank u
@Beethoven-n commented on GitHub (Aug 12, 2025):
it does not run, it segfaults
/tmp/.mount_Drop_DSS9THz/AppRun: line 6: 1379072 Segmentation fault (core dumped) LD_LIBRARY_PATH=$APPDIR/usr/lib:/usr/local/lib:/usr/lib $APPDIR/usr/bin/$program $@@Beethoven-n commented on GitHub (Aug 12, 2025):
do i need to do
./optimize-appimage.shafter?@DecDuck commented on GitHub (Aug 12, 2025):
Tauri should spit out an AppImage of its own, can you see if that runs?
@Beethoven-n commented on GitHub (Aug 12, 2025):
if it did, i wouldn't have made this PR
but i'll check
@DecDuck commented on GitHub (Aug 12, 2025):
The Tauri AppImage was failing because the exact library we're trying to fix was getting "stripped" out of it. It's the same fundamental issue, I'm just curious if it's a problem with our build script or the actual application.
@Beethoven-n commented on GitHub (Aug 12, 2025):
@DecDuck commented on GitHub (Aug 12, 2025):
Oh right, you're on Arch Linux. Tauri's AppImage builder doesn't play nice with anything other than Ubuntu 22 it seems.
Can you check if you can run the release binary directly?
@Beethoven-n commented on GitHub (Aug 12, 2025):
checked.
can't run it, it also segfaults
@DecDuck commented on GitHub (Aug 12, 2025):
Yeah, no idea then. Needs investigation.
[BUG] libayatana is a lazy dependency instead of a linked oneto [GH-ISSUE #1] [BUG] libayatana is a lazy dependency instead of a linked one@nek0d3r commented on GitHub (Mar 21, 2026):
This dependency is also the source of some problems I've been having trying to write a NixOS flake that wraps the AppImage using
pkgs.appimageTools:This is a bit out of my wheelhouse but I'm hoping I can figure this out as well!