@bionade24: I installed libsearpc, seafile and seafile-client from you repo, but the crash is still there. Am I still missing some package?
Search Criteria
Package Details: seafile-client 9.0.14-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: | 168 |
Popularity: | 0.000000 |
First Submitted: | 2012-12-10 17:34 (UTC) |
Last Updated: | 2025-07-25 11:57 (UTC) |
Dependencies (7)
- qt6-5compat
- qt6-base (qt6-base-gitAUR, 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 .. 44 Next › Last »
snack commented on 2021-10-11 09:41 (UTC) (edited on 2021-10-11 09:41 (UTC) by snack)
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.
bionade24 commented on 2021-10-11 09:18 (UTC)
@snack @wudu: Have you tried building every seafile related package in a clean chroot? Otherwise it's maybe caused by a broken build environment. https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot
If you don't want to do that yourself you can use the package from my CI/CD:
Build status: https://abs-cd.oscloud.info/cd_manager/seafile-client
https://wiki.archlinux.org/title/Unofficial_user_repositories#oscloud
snack commented on 2021-10-11 08:43 (UTC) (edited on 2021-10-11 08:43 (UTC) by snack)
@wudu It happens also to me. It didn't happen with 8.0.3 so I'd say it's a new bug.
wudu commented on 2021-10-11 08:38 (UTC) (edited on 2021-10-11 08:46 (UTC) by wudu)
I have installed the 8.0.4 version. On hovering (not clicking) the "gear" with the mouse to acces the options the program crashes. Didn't have an earlier version installed so I don't know if this problem existed before. Tried the same version in Ubuntu from the official repo without this problem in a VM.
When starting in a terminal I get:
GLib-WARNING **: 10:28:05.114: (../glib/glib/gerror.c:761):g_error_new_valist: runtime check failed: (domain != 0)
Followed by: 'seafile-applet' terminated by signal SIGSEGV
enos commented on 2021-10-04 10:33 (UTC)
Because of the checksum error I updated the package to 8.0.4. Pls also see comments at https://aur.archlinux.org/packages/seafile/.
bhartshorn commented on 2021-09-15 15:39 (UTC)
Can we get an optional dependency on qt5-wayland for those of us on Wayland?
Also, for those struggling with the validity check: updpkgsums
from pacman-contrib
makes short work of the problem, though don't get in the habit of using it blindly. It seems the seafile devs like to re-upload source packages.
Schroeffu commented on 2021-08-11 20:22 (UTC)
The sha256sum from depency seafile (v8.0.3.tar.gz) did also change, it is currently a83d5d301cf54819ab96ea0ab53824980efdf6727460b969ce3176b4c5109f6b
gromit commented on 2021-07-24 10:06 (UTC) (edited on 2021-07-24 10:09 (UTC) by gromit)
@urldog unfortunately this will be necessary:
- Clone packaging instructions:
$ git clone https://aur.archlinux.org/seafile-client.git
$ cd seafile-client
- Download the release from the official github page:
$ wget -O seafile-client-8.0.3.tar.gz https://github.com/haiwen/seafile-client/archive/v8.0.3.tar.gz
- Create the checksums for it:
$ sha256sum seafile-client-8.0.3.tar.gz
- Edit the PKGBUILD to match the shasum from Step 4 (line ~24)
- Install the package:
$ makepkg -si
So here is your step by step explanation, note that "$" means "run as normal user".
The underlying problem arises because the seafile people seem to re-release sometimes so the shasums of the ".tar.gz"-file change after release.
As a further comment I would say that you have to realize that what I described does circumvent the download and obviously the checksumming mechanism of the package itself and could be done in other ways, but all those would probably be a bad habit for you in the future (like ignoring these checksums at all).
If you need further help or have questions just post again.
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.