If i mark "start seeding",
and call the torrent file to save let say "bla.bla.iso".->

There is no .torrent added as extension to the filename.torrent.
This freezes KTorrent. (or at least when the torrent file has an .iso extension)

This bug is not present when i call the output file bla.bla-ISO, then KTorrent adds the expected *.torrent extension.

Another bug:

When i create a torrent of a folder with data,
and i browse one folder above the data,
and want to save the torrent as the same naming as in parent folder of the torrent where the data is in.->

The saving box gets me into the folder where the data of the torrent is saved instead of getting in the progress of making the torrent.

Another bug:

When creating a torrent which has not the exact same name field as the torrent folder creating the torrent from,
and open the torrent manually after creating the torrent.->

Torrent gets saved to a folder which has the same filename as the name field, instead of saving it to the folder created on.
(when "start seeding" is marked, this does not happen though)

This one *could* have something todo with a 99.9% bug i just experienced on demonoid. I will check on that in a few.
EDIT
Yep, when i give it the same naming as the directory name,
download the torrent from the site,
the torrent gets hashed 100%
(but this needs confirmation)

stoeptegel wrote:If i mark "start seeding",
and call the torrent file to save let say "bla.bla.iso".->

There is no .torrent added as extension to the filename.torrent.
This freezes KTorrent. (or at least when the torrent file has an .iso extension)

This bug is not present when i call the output file bla.bla-ISO, then KTorrent adds the expected *.torrent extension.

This appears to be standard behavior from the KDE dialog, I will add a safety check, so this doesn't happen.

stoeptegel wrote:Another bug:

When i create a torrent of a folder with data,
and i browse one folder above the data,
and want to save the torrent as the same naming as in parent folder of the torrent where the data is in.->

The saving box gets me into the folder where the data of the torrent is saved instead of getting in the progress of making the torrent.

This is the save dialog, I suggest you manually add the extension or if you don't like to do that, go to bugs.kde.org and file a bug report. The dialog is part of KDE, there is not much we can do.

stoeptegel wrote:Another bug:

When creating a torrent which has not the exact same name field as the torrent folder creating the torrent from,
and open the torrent manually after creating the torrent.->

Torrent gets saved to a folder which has the same filename as the name field, instead of saving it to the folder created on.
(when "start seeding" is marked, this does not happen though)

This one *could* have something todo with a 99.9% bug i just experienced on demonoid. I will check on that in a few.
EDIT
Yep, when i give it the same naming as the directory name,
download the torrent from the site,
the torrent gets hashed 100%
(but this needs confirmation)

Is this really a bug ? I mean KT uses the name in the torrent file when it opens a torrent, what name should it choose otherwise ? We have no idea that this torrent in question was created from a directory with a slightly different name.

When KT starts seeding this torrent immediatly, it knows where the original files are.

George wrote:Is this really a bug ?...

I am not sure to be honest, i am thinking that this naming option might do more harm than good. Because when you make a torrent of a directory "blaat", give it a name "bla", upload it to demonoid and download that torrent.-> it looks like all files that have multiple chunked files get 99.9% hashed/completed instead of 100%.

AFAIK other clients do this naming option automaticly and don't even give the option to the user. This way it can not go wrong. (not that it's a wrong option, it just looks like it does more harm than begin functional)

Also, i expected this naming option was only meant for the naming of the torrent in GUI, not for the actual storage folder. I guess i was wrong here.

stoeptegel wrote:

George wrote:Is this really a bug ?...

I am not sure to be honest, i am thinking that this naming option might do more harm than good. Because when you make a torrent of a directory "blaat", give it a name "bla", upload it to demonoid and download that torrent.-> it looks like all files that have multiple chunked files get 99.9% hashed/completed instead of 100%.

AFAIK other clients do this naming option automaticly and don't even give the option to the user. This way it can not go wrong. (not that it's a wrong option, it just looks like it does more harm than begin functional)

Also, i expected this naming option was only meant for the naming of the torrent in GUI, not for the actual storage folder. I guess i was wrong here.

I think you are right, we should remove the name option, it can only create confusion.

Thank you.

Another two issues with this torrent:

- I have to give is some time to be sure, but the torrent i uploaded seems to have one 99.99% completed peer that can not get on 100% for hours.
- There's also a problem with connecting to only one or two peers of the 20 leeching peers. (me as only seeder, ip-filter turned off)

stoeptegel wrote:Thank you.

Another two issues with this torrent:

- I have to give is some time to be sure, but the torrent i uploaded seems to have one 99.99% completed peer that can not get on 100% for hours.

Client ?

- There's also a problem with connecting to only one or two peers of the 20 leeching peers. (me as only seeder, ip-filter turned off

Are you sure they are online ?

George wrote:
Client ?

svn version
But it's my fault here. After this "naming bug", i reused the 99.9% which got 100% imported. Now i reused the backup and all it ok again. So it's all because of one bug + my lameness action.

- There's also a problem with connecting to only one or two peers of the 20 leeching peers. (me as only seeder, ip-filter turned off

Are you sure they are online ?[/quote]

Yes they are, but i figured that utorrent on wine has the same problem. So it's an issue outside KTorrent. (yes i am connectable)