![]() Registered Member ![]()
|
|
![]() Registered Member ![]()
|
Try manually copying/backup the contents of .kde/share/apps/ktorrent to some location. Then delete the dir and try to start KTorrent.
If Ktorrent don't crash now, try restarting it. If everyting still is OK, stop it and copy back one of the torX directories(Start with the lowest numbered one). Then start again. If it doesn't crash repeat until you have copied all torX directories. If some make it crash, remove them again and continue with the next. If none of the torX dirs cause the crash, try comparing your current plugins file to the old one. Try changing the new one to become like the old, by adding/removing lines one by one until it crashes. Finding out what cause the crash will be helpful for George when trying to fix the problem. |
![]() Registered Member ![]()
|
Hello again, sorry for takin so long to answear.
Ok.I deleted all files manually but still same.Kt crashes on startup. I installed it again from source and tried to find any warning messages. This is the only one i found: ./configure is OK but during "make" there is this warning message: "usr/lib/qt3/include private/qucom_ph:69 warning 'struct Qtype(name) has virtual functions but non-virtual destructor' " this message is displayed almost every 10 lines during "make" procces It is not a single line, but a block of warning messages(about 8 lines)like this: usr/lib/qt3/include/*/qucom_ph:* warning 'struct Qtype(*) has virtual functions but non-virtual destructor' " I dont know if this could help.This is all i found ![]() |
![]() Moderator ![]()
|
Those warnings can be ignored, try deleting ~/.kde/share/apps/ktorrent (maybe back it up if there is valuable data in there). If it still crashes : ./configure --enable-debug=full make make install Then when it crashes, you should get a usefull backtrace, post that here. |
![]() Registered Member ![]()
|
I'm (trying to) us(e)ing ktorrrent-1.1 with kde-3.5 on amd64. I have exactly this problem - after some random time, network connection drops and has to be reinitialized (interface down/up). I suspect my WiFi router (Motorola SBG900), as, after the network gets stuck, all computers on the WiFi cell lose their connection.
However, I found that only ktorrent causes this behavior. I have an amule client running under heavy load for a long time, without any problems. Other network programs are also working fine. |
![]() Moderator ![]()
|
You should at least upgrade to 1.2, and if this still happens, cap your bandwith. If the router dies under the heavy traffic, the only thing you can pretty much do is limit the bandwith KT uses. |
![]() Registered Member ![]()
|
I don't think this has anything to do with bandwidth. I've upgraded to 1.2, capped both u and d bandwidth to some small figure and left only one active torrent. The problem persists. In fact, I checked with ethereal - the router always drops connection after ktorrent's <interested> message.
What is more interesting - some torrents are causing this to happen more often than others. I can download some large torrents without any problems and bandwidth capping, while other torrents are breaking the network each couple of kilobytes. |
![]() Registered Member ![]()
|
Some additional info.
I picked up especially nasty torrent which ktorrent was basically unable to download (because of this network thing). I tried it with other clients on my machine, with following results: ctorrent - same problems as ktorrent bittornado - downloads without problem, but low speed for some reason azureus - no problems at all, high speed Now, there can be various explanations for this (I did a rather haphazard testing, after all). Still, the results are rather weird. |
![]() Moderator ![]()
|
|
![]() Registered Member ![]()
|
Registered users: bancha, Bing [Bot], Google [Bot], Sogou [Bot]