Uploading files doesn't work on Windows

[flipie]

I'm running Nicotine-Plus 1.2.7.1 on a Linux machine. Uploading works fine. My download list got a bit big and the slow machine cannot handle it anymore. Fortunately, the Linux machine shares files over SMB. So I've switched Nicotine-Plus temporarily to Windows. Accessing my files over SMB (including with Windows Explorer) works fine on a Windows machine I'm running Nicotine-Plus 1.2.7.1 on. I can not only see them, but also use them. So far so good.

But, I have a strange problem using Nicotine 1.2.7.1 on the Windows machine. I cannot upload files. Files queue up in the upload tab but no upload ever starts. People can browse me, and port forwarding is set up correctly. It seems that Nicotine-Plus can see the files, but they're always 0 bytes. If I right click and click 'retry' to initiate the transfer it says for example 8 / 0 bytes and then 'finished'. Well, that didn't work...

[anonymous]

sometimes it starts when you cancel/abort the transfer again

[anonymous]

oh? not here.

I was able to reproduce the problem under 1.2.8

[Giovanni (HumanScum @…]

here same problem but on linux, when i manually upload files or directory to user, first it give me an error and when i retry them it says "finished" and CPU goes to 100% when actually nothing has been transfered. CPU stands at top usage until i close nicotine+, sometimes when i restart it the files i uploaded start to transfer fine. i run nicotine 1.2.8+dfsg-1 on debian unstable

[flipie]

FWIW, able to reproduce w/Nicotine 1.2.8, same Windows client, plus FreeBSD + Samba 3.0.25a sharing the files over the network. Exactly same thing happens. I do not notice 100% CPU usage nor do I upload manually.

[flipie]

Slap me. I had the speed limiter at 0. Put it higher, seems to work now.

[flipie]

Downgraded to recommended GTK version, rebooted. Seems to work fine again, then it doesn't. Reboot is not necessary; restarting the client solves the problem temporarily. It seems when it occurs it counts for any _new_ uploads which all have this problem. Old ones do not have this problem. More people are bitten by this bug btw, I'm not sure it is Samba-related.

I had to downgrade my Samba due to this Samba bug in 3.0.25 bugzilla.samba.org/show_bug.cgi?id=4715

[hallucinogirl]

Running Nicotine+ 1.2.9svn (on Windows XP with SP2) with similar problems. It appeared to just quit auto-initializing transfers after an indefinite period of time. Upon manual Retry for transfers that failed for any reason, the files were measured as 0 bytes and upon more manual retries would quickly read (in error) as Finished. Restarting the application cured this but was necessary several times a day whilst monitoring inbetween.

I found the workaround to be to use FIFO instead of Round Robin while also limiting upload slots and upload speed per transfer accordingly to just below user's maximum available upload bandwidth. (For instance, even with my measly 384k DSL connection I can safely limit myself to 2-3 users at 10-15kbps per user and I don't wake up to too many complaints). ;)

Recommend users to experiment with the FIFO and other Upload Queue settings to see what works best for them.

[dziwka]

this solutios helped me (my ver. of n+ 1.2.9 & win xp pro sp2): 1. uninstall bad version of gtk 2. uninstall nicotine (ur private data will be saved don't worry) 3. restart windows 4. install gtk recommended nicotine-plus.sourceforge.net (downloads.sourceforge.net/gladewin32/gtk-2.10.11-win32-1.exe) 5. install nicotine 1.2.9 now uploads work fine for me with round robin and FIFO (my choice) greets

[dziwka]

after my last solution, i still have got probs with upload, I think will be back to slsk client

[offhand]

obsolete client version. hopefully, one day, there will be a new windows installer.