Package Details: seafile-client 9.0.11-1

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: 2024-11-14 17:07 (UTC)

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.

Latest Comments

« First ‹ Previous 1 .. 18 19 20 21 22 23 24 25 26 27 28 .. 44 Next › Last »

ToK commented on 2017-04-27 14:44 (UTC)

Still not working. I tried installing on a new system (and removing ~/.ccnet and ~/seafile/.seafile). I tried starting seaf-daemon after starting the applet. I would think it should be my private server. But my Macbook syncs fine with seafile-client 6.0.4...

limecat commented on 2017-04-27 14:08 (UTC)

I also had this error: seafile-applet: relocation error: seafile-applet: symbol _Znwm, version Qt_5 not defined in file libQt5WebEngineCore.so.5 with link time reference Uninstalling everything (ccnet, seafile-client, all deps etc.) and reinstalling got the applet going again, but still gave me the Transport error on trying to sync with my existing libraries. Manually starting the seaf-daemon solves that as a workaround, and I can confirm that rm -rf on ~/.ccnet and ~/Seafile/.seafile-data makes everything work ok again.

eolianoe commented on 2017-04-27 13:52 (UTC)

@blubbblubb: everything is fine here, with the qt5-webengine-5.8.0-6. @polslinux: I made the PKGBUILD for seadrive [a], but I've no idea how to make it works... (if you have any idea please comment on the seadrive-gui page) [a] https://aur.archlinux.org/packages/seadrive-gui/

blubbblubb commented on 2017-04-27 11:52 (UTC) (edited on 2017-04-27 11:53 (UTC) by blubbblubb)

probably a qt5-webengine or seafile source problem but it cant hurt to mention it here as well, with the newest qt5-webengine (qt5-webengine-5.8.0-6) it is not possible to start the seafile-applet (all the newer qt5 packages, the ones in staging/beta also show problems) seafile-applet: relocation error: seafile-applet: symbol _Znwm, version Qt_5 not defined in file libQt5WebEngineCore.so.5 with link time reference I never submitted a bug for a package before so I will need to read up on the guidelines before doing so, if anyone feels like reporting this in the right place feel free to do so ;)

eolianoe commented on 2017-04-27 11:31 (UTC)

Nice that you find away to solve the problem. @polslinux: I'll look at this new client and see if it's easy to package it on linux

polslinux commented on 2017-04-26 18:53 (UTC)

@eolianoe: interested in packaging also the seadrive client? :) thanks!

blubbblubb commented on 2017-04-26 18:27 (UTC) (edited on 2017-04-26 18:27 (UTC) by blubbblubb)

Only removing ~/.ccnet did not work for me. I had to remove ~/.ccnet and ~/Seafile/.seafile-data All libraries are syncing now.

snack commented on 2017-04-26 17:04 (UTC)

Removing ~/.ccnet fixed the problem on my system: seaf-daemon no longer segfaults and sync works again. I had to re-configure the account and sync libraries: in doing so I overwrited the current version on my pc with the old version put on the server 4 hours ago. It was not a big issue for me but could be for others, so take care (I suggest to create a local backup of your libraries before syncing).

blubbblubb commented on 2017-04-26 16:12 (UTC) (edited on 2017-04-27 09:34 (UTC) by blubbblubb)

tl:dr Workaround: manually start seaf-daemon after launching the client/applet I got the same segfault with seaf-daemon, also did a full reinstall on my System and updated my Server to 6.0.9 Workaround for now: If i start the seaf-daemon from hand again with the client (applet) already running it seems to be running fine.

eolianoe commented on 2017-04-26 15:39 (UTC)

@ToK, @snack: just made a 'yaourt -Rncds libsearpc && yaourt -S seafile-client' and everything is going fine. No idea why there are failures on your systems :(