Package Details: seafile-client 6.0.6-2

Git Clone URL: https://aur.archlinux.org/seafile-client.git (read-only)
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
Conflicts: seafile-client-qt5
Provides: seafile-client-qt5
Submitter: Localizator
Maintainer: eolianoe (edacval)
Last Packager: eolianoe
Votes: 123
Popularity: 3.808076
First Submitted: 2012-12-10 17:34
Last Updated: 2017-05-28 18:55

Latest Comments

Psynigmashi commented on 2017-05-28 04:23

Thank you @Dezponia. My seafile program wasn't launching for a few days now and after rebuilding it with yaourt, it's now working perfectly fine.

eolianoe commented on 2017-05-26 09:15

@Captain_Rage: openssl-1.0 is already resolved by the qt5 deps.

@ndandanov & @noEntry: as @Dezponia said a rebuild resolves the new soname/symbols, no need of a downgrade, see the wiki [a].

[a] : https://wiki.archlinux.org/index.php/Frequently_asked_questions#What_if_I_run_a_full_system_upgrade_and_there_will_be_an_update_for_a_shared_library.2C_but_not_for_the_apps_that_depend_on_it.3F

ndandanov commented on 2017-05-26 07:55

Thank you, @Dezponia!

After upgrading openssl-1.0 and qt5-base, it was a matter of just running:

pacaur -S seafile-client --rebuild


Now it works properly.

Dezponia commented on 2017-05-26 06:55

@ndandanov

Try simply re-installing the seafile-client package. This is how I did it with the AUR-Helper "aurget".

aurget -S seafile-client

That launched a re-install and thus also a rebuild since its an AUR package. If it doesn't work that way with pacaur then I'll have to direct you to get help from the pacaur people. If nothing else you can just build it manually as per the Arch wiki (https://wiki.archlinux.org/index.php/Arch_User_Repository#Installing_packages)

ndandanov commented on 2017-05-26 06:47

@Dezponia,

Sorry if this question is too basic, but could you please provide a simple example how one could rebuild the package?
Perhaps use this information:
https://wiki.archlinux.org/index.php/downgrading_packages#Rebuild_the_package?

I am using pacaur if this has any importance. I'm relatively new to Arch, but have some experience with Debian-based distros. :)

Thanks!
Nikolay

Dezponia commented on 2017-05-25 21:53

Simply rebuilding seafile-client fixed this issue for me earlier today. Using the latest libraries here. Perhaps try that before downgrading.

ndandanov commented on 2017-05-25 21:50

After the latest updates of openssl-1.0:

[2017-05-25 23:52] [ALPM] upgraded openssl-1.0 (1.0.2.k-3 -> 1.0.2.k-4)
[2017-05-26 00:27] [ALPM] upgraded openssl-1.0 (1.0.2.k-4 -> 1.0.2.l-1)

I cannot launch the Seafile client GUI:

[nikolay@nikolay-t440p ~]$ seafile-applet
seafile-applet: /usr/lib/libcrypto.so.1.0.0: version `OPENSSL_1.0.2d' not found (required by seafile-applet)

I had to downgrade both openssl-1.0 and qt5-base:

[nikolay@nikolay-t440p ~]$ sudo pacman -U /var/cache/pacman/pkg/openssl-1.0-1.0.2.k-3-x86_64.pkg.tar.xz
[nikolay@nikolay-t440p ~]$ sudo pacman -U /var/cache/pacman/pkg/qt5-base-5.8.0-11-x86_64.pkg.tar.xz

(Source: https://wiki.archlinux.org/index.php/downgrading_packages)

Now the Seafile client seems to be running properly. :)

noEntry commented on 2017-05-25 21:43

Any way to fix this issue? Installing openssl-1.0 did not solves this issue.

seafile-applet: /usr/lib/libcrypto.so.1.0.0: version `OPENSSL_1.0.2d' not found (required by seafile-applet)

Captain_Rage commented on 2017-05-25 19:05

Package openssl-1.0 should be marked as a dependency.

a-bostaurus commented on 2017-05-15 13:59

I have to apologize. It's not a problem of seafile, but a problem of my special configuration. The package is ok, Manjaro is okay, my system got some problems ...

All comments