Closed vpereira closed 6 years ago
I think there is a problem with QT5.. on Fedora 22, I had the same problem. It just worked after that I updated QT, to QT5.5..
The seafile-applet crashes with a segmentation fault error as soon as I try to access it through the tray icon. I've upgraded my opensuse 13.2 to QT5.5 to no avail.
hm thats already something new.. which seafile-applet are you using? we have some compiled on buildserver:
http://download.opensuse.org/repositories/Cloud:/Seafile/openSUSE_Tumbleweed/Cloud:Seafile.repo http://download.opensuse.org/repositories/Cloud:/Seafile/openSUSE_13.2/Cloud:Seafile.repo http://download.opensuse.org/repositories/Cloud:/Seafile/openSUSE_13.1/Cloud:Seafile.repo
Note that in fedora it crashed as well with segmentation fault and as soon as i updated my QT to 5.5 it worked as expected.. there ate some QT 5.5 on build server as well, I've got them from:
http://download.opensuse.org/repositories/KDE:/Qt55/openSUSE_Factory/KDE:Qt55.repo http://download.opensuse.org/repositories/KDE:/Qt55/openSUSE_13.2/KDE:Qt55.repo
I'm trying now in a factory box with kde instead of gnome..
wow good news. On a tumbleweed box, running QT 5.5 I was able to compile and run the seafile-applet without problems.. I will push it to the buildserver.. I think the problem is to compile seafile-client with a version of QT and run with another.. Like compile with 5.0 and run with 5.5.
I'm using the applet as given in the Cloud repo for 13.2. Can you push it to 13.2 Cloud repo as well?
https://build.opensuse.org/project/show/home:vpereirabr:Seafile
however I'm not sure if it will work. I tested on a KDE opensuse 13.2 and it worked, however on a gnome based 13.2 the problem still there.. maybe some runtime lib is missing.. dunno.
On Mon, Sep 28, 2015 at 9:21 AM, tneo notifications@github.com wrote:
I'm using the applet as given in the Cloud repo for 13.2. Can you push it to 13.2 Cloud repo as well?
— Reply to this email directly or view it on GitHub https://github.com/haiwen/seafile-client/issues/722#issuecomment-143658737 .
I installed you're compiled file, but the applet is not showing the icon even. Nothing seems to be happening, although ksysguard reports it is running.
I am using the new Leap 42.1 KDE and would like to use the seafile client. Please let me know how to stay updated for Leap version. thanks
It seems that this problem is quite rare. I've got the same symptoms: I've installed seafile frome the http://download.opensuse.org/repositories/Cloud:/Seafile/openSUSE_Tumbleweed/ and it did not work: seafile window did not appear at all.
So I've decided to convert .deb package from the seafile website into rpm. It was quite easy, but I've installed additional libcrypto and libssl, because converted rpm was requiring libcrypto.so.1.0.0. Those packages did not fix that requirement, so I've just ignored it. After that I've figured out that all libs was installed into /usr/libs, while seafile-applet was looking them into /usr/lib64 (I honestly don't know why), so I've symlinked them. At the end I was able to run seafile, but with corrupted systray icon.
I think that it is possible to create rpm file for opensuse from the original deb. I almost did it, but I don't have any experience with packaging, and I am quite new in opensuse and rpm distros at all. But I think if someone would be able to package it properly and upload to the opensuse repo, it would be great. If someone need, I can give upload my rpm.
@vpereira Hi, are you using the opensuse build service? Any luck compiling it to target leap or are you focusing on another version and architechture?
You should at the repository to zypper:
zypper addrepo http://download.opensuse.org/repositories/Cloud:Seafile/openSUSE_Tumbleweed/Cloud:Seafile.repo
zypper refresh
Similar repositories for other openSuse platforms can be found here.
Now install needed packages:
zypper install seafile seafile-client ccnet python-pysearcpc
Append /usr/sbin to your PATH variable (e.g. in fish shell):
set -x PATH $PATH /usr/sbin
At least start seafile-client and set up configuration. This works for me under Thumbleweed.
I am having the same problems as @Gribs.
I installed seafile-client via zypper, as @werneazc described. But after I launch it, I see nothing at all. When I remove the old config files, I can see the Window to specify the server. But afterwards there is nothing. Not even a tray icon. The synchronization is not working aswell.
I am using Suse Tumbleweed.
Update:
I also activated the Debug log with export SEAFILE_DEBUG=all
without success. I don't get any log messages.
Have you added the /usr/sbin path to your PATH variable?
Add
export PATH=/usr/sbin:$PATH
into your .bashrc file in your home folder. Restart and it should work.
It's important to edit the PATH. I set up a new PC with Leap 42.2 and my solution worked also there.
@werneazc I've just tried updating my path but still no GUI or output on the console. :(
What package repository did you install? Have you used the right repository which fit to your installed opensuse version?
For Leap 42.2 I used the repository
http://download.opensuse.org/repositories/Cloud:/Seafile/openSUSE_Leap_42.1/Cloud:Seafile.repo
I use opensuse with plasma environment. I haven't tested my approach with other styles? Then I continued with the installation as described.
I'm using Tumbleweed.
sudo zypper addrepo http://download.opensuse.org/repositories/Cloud:Seafile/openSUSE_Tumbleweed/Cloud:Seafile.repo
sudo zypper refresh
sudo zypper install seafile-client
seafile-applet
^C (hangs)
@mhingston I don't understand your comment. Have you also installed all mentioned requirements mentioned above in my first post?
Now install needed packages:
zypper install seafile seafile-client ccnet python-pysearcpc
@werneazc thanks, I was missing python-pysearcpc
@mhingston Don't mention it.
I have my seafile working with the mac client. Everything works as expected
However on Linux I have the following problem. I was able to compile the code, but as soon as I start it, calling seafile-applet, I juse see the window to configure the default folder, and after that, I don't see the next options, like to configure my server, user and password.. is that the expected behavior, known problem or regression?