Red Hat Bugzilla – Bug 377201
conduit removes symlinks
Last modified: 2009-01-09 02:24:06 EST
Description of problem:
Every time I try to sync my Pictures and Documents folders, which are symlinked
to some other HDD's folder, conduit removes the symlink and it turnes them into
a text file containing the folder name.
Version-Release number of selected component (if applicable):
Install counduit and configure a sync of a symlink that points to a folder
containing images to flickr and picassa and, also, a symlinked folder that
contains documents (OOo & txt) to a Box.net account.
Steps to Reproduce:
1. register a Box.net account
2. register a flickr account
3. rgister a picassa account
4. install conduit: su -c 'yum install conduit'
5. make sure you don't have a "documents" and "pictures" folder on your home
directory and create the symlinks to documents and pictures folder: ln -s
/path/to/pictures ~/pictures && ln -s /path/to/documents ~/documents
6. launch condutil: application>Accesories>Condutil
7. configure it to sync your symlinked pictures folder, at your home directory,
to flickr and picassa
8. configure condutil to sync your symlinked documents folder, at your home
directory, to Box.net
9. start syncronization
Your symlinked folders, at your home directory, turn into text files containing
the folder name
Your symlinked folders should be synced with the services appointed.
Thanks for the detailed bug report. If you have time, please test with the
latest conduit due to be released into Fedora in a few days.
You can do this with:
su -c "yum --enablerepo=updates-testing update conduit"
I will. I'll report back then.
Ok, confirmed, even on the update, this happens... And, also, it fails to
refresh after a sync... but that's another bug ;=s
I talked briefly with John Carr and these were his comments:
<Jc2k> we've refactored the file stuff a lot in 0.3.5 so i dont know if im just
failing at recreating it or if its gone..
<Jc2k> can you recreate it with a folder to folder sync?
<Jc2k> also, it sounds like the config code is implicated.
<Jc2k> ... could you ask him to post a screenshot of how he configured the
folder dataprovider, and if it happens if you do symlinked folder to symlinked
He is on the CC: list now so he'll get your comments directly.
Ok, first of all, I must say, I unninstalled it after my last post.
I installed the test version, which is not 0.3.5, but 0.3.4-2...
Couldn't reproduce it with a local folder to local folder setup. In fact, it
When I tried syncing the symlinked folder to flickr, it didn't remove the
symlink anymore, but it never finished the sync. It got to:
1st try: 1%
2nd try: 6%
3rd try: 4%
With a "Error Synchronizing" message in both items.
Tried to do it, also, with Facebook, but it didn't even give me configuration
options and, when trying to sync or refresh, it froze.
Created attachment 262121 [details]
screenshots that you guys asked
This contains screenshots of the config windows you asked and the screenshot of
a ls -l and cat done to the former symlink dir
Ok, something strange happened. After I restarted my computer (note that I
reinstalled conduit and it's auto-starting) my Pictures folder truned into a
file. I will post the screenshots in a tar.bz2 file.
Are you still seeing this with the latest release 0.3.11.1-1?
This is the version I have... I'll just wait until it gets updated.
Ok, sorry, I installed the testing version. Everything goes well until the
"Conduit Login Manager" starts. It shows nothing... blank page...
and the sync status shows as "OK" on the folder but "error refreshing" on the
I tried using flickr and facebook
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '8'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 8's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 8 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.