kmldonkey downloads disappearing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mldonkey (Ubuntu) |
Incomplete
|
Low
|
Unassigned |
Bug Description
I have a strange new problem after upgrade from kubuntu 5.4 to kubuntu
5.10 (kde 3.4.2 > kde 3.4.3): the files that I downloaded via Kmldonkey
(edonkey2000 network) do not go into ~/.kmldonkey/
simply disappear. They no longer appear in the downloads list of
kmldonkey, but they are not in either temp (jugding by the number of
files that should be there - since filenames are not recognizable) or
incoming folders either. they do, however, appear on the list of
uploads of Kmldonkey. I tried to do searches by exact name with kfind,
to no avail.
I have a
~/.kmldonkey/
special dir for all kmldonkey files with subdirs
~/.kmldonkey/
~/.kmldonkey/
~/.kmldonkey/temp
The incoming files used to go to incoming, but they no longer do. The files
in incoming also do not appear in the downloads view... After a new fresh clean install the
incoming dir is not even created, and the downloaded files still disappear.
The files that I have downloaded fully and that have disappeared (I did
search, and it turned in nothing) DO APPEAR in the Uploads view of
KMldonkey. But, as I said, I CANNOT FIND THEM IN ANY WAY AT MY DISPOSAL.
Changed in kdenetwork: | |
assignee: | nobody → jr |
affects: | kdenetwork (Ubuntu) → mldonkey (Ubuntu) |
Changed in mldonkey (Ubuntu): | |
importance: | Medium → Low |
status: | Incomplete → New |
assignee: | Jonathan Riddell (jr) → nobody |
OK, so I did find them finally. they started to go to one of the shared directories, that was on another file system, therefore I did not locate those via kfind.
I still don't know why they changed the place where they would go, and I did not take care to have the backup of the config files, both before and after the upgrade (I did quite a lot of experimenting with kmldonkey since then). Therefore I cannot help with solving this problem, and since there is no one having it (or no one has joined this bug report), I would recommend to close it as unconfirmed.