Bug 829821
Summary: | sparkleshare shows empty "recent changes" | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | markusN <neteler> |
Component: | sparkleshare | Assignee: | Nikos Roussos <comzeradd> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 17 | CC: | comzeradd, palango |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-07-23 20:29:06 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
markusN
2012-06-07 15:38:56 UTC
I have now tried with sparkleshare 0.8.4 selfcompiled from GIT, same problem. Hence I suspect a mono or git problem in F17 rather than a Sparkleshare problem. The messages when launching it in a terminal appear to be normal and connection to my data repo established. Same here, however today I built version 0.9 and it works fine there. Seems like an update should solve that problem. sparkleshare-0.9.0-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/sparkleshare-0.9.0-1.fc17 Package sparkleshare-0.9.0-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing sparkleshare-0.9.0-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-10342/sparkleshare-0.9.0-1.fc17 then log in and leave karma (feedback). sparkleshare-0.9.0-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. |