I also suspect that something is not working as intended after the last upgrade of openssl. The Seafile desktop client keeps showing a 'Transport Error' message as well as a yellow icon ("not synced") for all my libraries.
~/.ccnet/logs/applet.log:
[2017-04-29 14:47:53][Sea RPC] Bad response: 102 processor is dead.
[2017-04-29 14:47:54][Sea RPC] Bad response: 102 processor is dead.
[2017-04-29 14:47:54]failed to get repo list: Transport Error
[2017-04-29 14:47:54][Sea RPC] Bad response: 102 processor is dead.
Looks like something keeps crashing, but I haven't managed to pinpoint it. @woffs: I'm also inclined to think so! Is this something that we can change or a problem upstream?
EDIT:
The Seafile client works perfectly after upgrading the packages to 6.0.6.
Search Criteria
Package Details: seafile 9.0.11-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/seafile.git (read-only, click to copy) |
---|---|
Package Base: | seafile |
Description: | An online file storage and collaboration tool |
Upstream URL: | https://github.com/haiwen/seafile |
Licenses: | GPL2 |
Conflicts: | seafile-server |
Provides: | seafile-client-cli |
Submitter: | eolianoe |
Maintainer: | Joffrey |
Last Packager: | Joffrey |
Votes: | 111 |
Popularity: | 0.000000 |
First Submitted: | 2016-08-11 16:38 (UTC) |
Last Updated: | 2024-11-14 17:06 (UTC) |
Dependencies (8)
- fuse (fuse2)
- libevent (libevent-gitAUR)
- libsearpcAUR
- libwebsockets
- python-future
- sqlite (sqlite-fossilAUR)
- intltool (make)
- vala (vala-gitAUR) (make)
Required by (2)
Sources (2)
Latest Comments
« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 .. 47 Next › Last »
Captain_Rage commented on 2017-04-29 12:56 (UTC) (edited on 2017-05-19 12:37 (UTC) by Captain_Rage)
woffs commented on 2017-04-28 21:05 (UTC) (edited on 2017-04-28 21:10 (UTC) by woffs)
It builds, but it crashes at start. I guess the reason is because libssh2.so and libcurl.so link against openssl-1.1 while seafile wants openssl-1.0
Apr 28 23:07:34 hostname systemd-coredump[13282]: Process 13270 (seaf-daemon) of user 1000 dumped core.
Stack trace of thread 13278:
#0 0x00000000b6a1ccc6 X509_NAME_cmp (libcrypto.so.1.1)
#1 0x00000000b6a1cde2 X509_subject_name_cmp (libcrypto.so.1.1)
#2 0x00000000b6a1dcf6 n/a (libcrypto.so.1.1)
#3 0x00000000b748d020 OBJ_bsearch_ex_ (libcrypto.so.1.0.0)
#4 0x00000000b7513df0 sk_find (libcrypto.so.1.0.0)
#5 0x00000000b75625a0 X509_OBJECT_retrieve_match (libcrypto.so.1.0.0)
#6 0x00000000b7562716 X509_STORE_add_cert (libcrypto.so.1.0.0)
#7 0x0000000008057e10 n/a (seaf-daemon)
#8 0x00000000080c487c n/a (seaf-daemon)
#9 0x0000000008057c7c n/a (seaf-daemon)
#10 0x00000000b70b3d80 n/a (libcurl.so.4)
#11 0x00000000b70b4ed9 n/a (libcurl.so.4)
#12 0x00000000b70b7d39 n/a (libcurl.so.4)
#13 0x00000000b706d3e0 n/a (libcurl.so.4)
#14 0x00000000b707ec6b n/a (libcurl.so.4)
#15 0x00000000b70937a0 n/a (libcurl.so.4)
#16 0x00000000b7094851 curl_multi_perform (libcurl.so.4)
#17 0x00000000b708a22b curl_easy_perform (libcurl.so.4)
#18 0x0000000008058e7a n/a (seaf-daemon)
#19 0x000000000805d70b n/a (seaf-daemon)
#20 0x00000000b730be7d n/a (libccnet.so.0)
#21 0x00000000b7180118 n/a (libglib-2.0.so.0)
#22 0x00000000b717f6aa n/a (libglib-2.0.so.0)
#23 0x00000000b70460f4 start_thread (libpthread.so.0)
#24 0x00000000b6f6e4a6 __clone (libc.so.6)
Stack trace of thread 13270:
#0 0x00000000b7705cd9 __kernel_vsyscall (linux-gate.so.1)
#1 0x00000000b6f6eb6a epoll_wait (libc.so.6)
#2 0x00000000b72c3428 n/a (libevent-2.0.so.5)
#3 0x00000000b72ac3a4 event_base_loop (libevent-2.0.so.5)
#4 0x00000000b72adc30 event_loop (libevent-2.0.so.5)
#5 0x00000000b72adc56 event_dispatch (libevent-2.0.so.5)
#6 0x00000000b730ad04 ccnet_main (libccnet.so.0)
#7 0x000000000804f109 n/a (seaf-daemon)
#8 0x00000000b6e99366 __libc_start_main (libc.so.6)
#9 0x000000000804f286 n/a (seaf-daemon)
fordprefect commented on 2017-04-26 13:35 (UTC)
@urldog: please make sure you updated the repos and also your system. openssl-1.0 definitely is in the repos.
eolianoe commented on 2017-04-26 13:35 (UTC)
@urldog: for i686 and x86_64 openssl-1.0 is in extra for the other architecture I can't tell anything
urldog commented on 2017-04-26 13:31 (UTC)
Seems not to work as of Apr 26 2017. openssl-1.0 seems not to be there
Revelation60 commented on 2017-04-24 20:54 (UTC)
This package does not compile with the latest openssl.
eolianoe commented on 2017-03-17 19:39 (UTC)
@Popkornium18: Done for all the seafile packages
Popkornium18 commented on 2017-03-17 10:48 (UTC)
Could you add 'aarch64' to the list of supported architectures on all seaf-cli related packages? I've been using it for about a year I think and never had a problem with the compiled program. It's just that adding it manually to the PKGBUILD is a little annoying.
StraxKvar commented on 2017-02-12 17:19 (UTC)
Installs fine now. Thanks!
StraxKvar commented on 2017-02-12 11:56 (UTC)
When building seafile-client, it looks to use seafile-6.0.2.tar.gz as a dependency. But the current version is seafile-6.0.3.tar.gz. Also the checksum for 6.0.3 is currently broken: https://aur.archlinux.org/packages/seafile/, as in comments below. Please fix.
Pinned Comments