@bionade: I imported and trusted the key 289AD6AA32857A04ABA587417EAC11ACDBCFBCEB, then pacman -Syy then pacman -S seafile-client seafile libsearpc. Still the same issue.
Search Criteria
Package Details: seafile-client 9.0.18-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/seafile-client.git (read-only, click to copy) |
|---|---|
| Package Base: | seafile-client |
| Description: | GUI client for synchronizing your local files with seafile server |
| Upstream URL: | https://github.com/haiwen/seafile-client |
| Licenses: | Apache |
| Submitter: | Localizator |
| Maintainer: | Joffrey |
| Last Packager: | Joffrey |
| Votes: | 173 |
| Popularity: | 1.19 |
| First Submitted: | 2012-12-10 17:34 (UTC) |
| Last Updated: | 2026-04-16 09:08 (UTC) |
Dependencies (7)
- qt6-5compat
- qt6-base (qt6-base-gitAUR, qt6-base-hifpsAUR, qt6-base-headlessAUR)
- qt6-webengine
- seafileAUR
- cmake (cmake3AUR, cmake-gitAUR) (make)
- qt6-tools (make)
- gtk-update-icon-cache (gtk-update-icon-cache-gitAUR) (optional)
Required by (0)
Sources (2)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 45 Next › Last »
snack commented on 2021-10-16 11:26 (UTC)
snack commented on 2021-10-16 11:01 (UTC)
@bionade: I added your [oscloud] repo to my pacman.conf, but when I download its db pacman says:
error: oscloud: key "289AD6AA32857A04ABA587417EAC11ACDBCFBCEB" is unknown
This key is different from the one listed in archwiki:
Key-ID: CB222E7EBC11D682AAC8B317A4A0D73114FDE6FC
Should I trust it? (not a gpg expert here, so sorry if the question is a dumb one). Thanks
bionade24 commented on 2021-10-16 10:27 (UTC)
@snack I would say that should work, too. But you'll only be sure with PGP integrity.
Now upgraded my 2nd device, works fine too.
snack commented on 2021-10-14 08:13 (UTC)
@bionade24: I downloaded the packages from your site manually and the pacman -U.
snack commented on 2021-10-14 08:10 (UTC)
@bionade24: I downloaded the packages from your site manually and the pacman -U.
bionade24 commented on 2021-10-13 20:46 (UTC) (edited on 2021-10-16 10:27 (UTC) by bionade24)
@snack @wudu @ReneS I now updated my system and seafile to 8.0.4. As I've already guessed, it works fine for me and it seems to be a super tricky issue with dirty build environments. So either build in clean chroots or use my repo, but it's not the pkg's fault.
@Joffrey Maybe change the pinned comment to building in a clean chroot.
@snack: You sure youre cache didn't fuck that up? Try pacman -Rsc seafile-client seafile libsearpc && pacman -Scc && pacman -S seafile-client after you added my repo.
Edit: Now also updated my 2nd machine, everything works fine.
ReneS commented on 2021-10-13 15:22 (UTC)
Updated from v8.0.3 to v8.0.4 recently. Now it crashes, this is how you can reproduce the issue:
- Start Seafile
- In the Seafile window, hover the mouse over the settings button
Reproduced on 2 arch installations.
This is the stack trace: https://pastebin.com/AMmc9pTZ
snack commented on 2021-10-11 09:41 (UTC) (edited on 2021-10-11 09:41 (UTC) by snack)
@bionade24: I installed libsearpc, seafile and seafile-client from you repo, but the crash is still there. Am I still missing some package?
bionade24 commented on 2021-10-11 09:27 (UTC)
@snack: You have to reinstall every seafile related package, only reinstalling seafile-client obviously can't help if the libraries are broken.
snack commented on 2021-10-11 09:23 (UTC)
@bionade24: I built it with yay as always did. So I tried installing the packages from your repo but that didin't fix the problem.
Pinned Comments
Joffrey commented on 2021-05-30 20:06 (UTC) (edited on 2021-05-30 20:11 (UTC) by Joffrey)
Please, when you have compilation or execution errors, recompile each component without using an AUR helper before reporting an issue.