Hello!

First, sorry about my poor english. I'm user of ktorrent from some month ago, the speed doens't good, but it consume low cpu. I'm user of ubuntu dapper amd64 6.0.6LTS, and i have downloaded and updated my KTorrent 2.0.1 (the official nowadays)... when Ktorrent starts all seems ok (downloading 70KB/80KB in a few seconds) but it crash unknowing when....

I paste the output : )

lordek@leviathan:~$ ktorrent
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 147
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 147
Minor opcode: 3
Resource id: 0x0
Failed to open device
kio (KMimeType): WARNING: KServiceType::offers : servicetype ThumbCreator not found
kio (KMimeType): WARNING: KServiceType::offers : servicetype ThumbCreator not found
kio (KMimeType): WARNING: KServiceType::offers : servicetype ThumbCreator not found
kio (KMimeType): WARNING: KServiceType::offers : servicetype ThumbCreator not found

Here the client run ok ....


And here it crashes...
lordek@leviathan:~$ ktorrent: symbol lookup error: /usr/lib/libktorrent.so.0: undefined symbol: _ZNK8KNetwork10KIpAddress12hostIPv4AddrEb

I run it with GNOME.

Try running KTorrent with:

ktorrent --debug

and then paste the output here.

We had two thread about something like it. "Ktorrent crash after a while - Symbol lookup error" and "2.0.2 (from Suse 10.1 rpm) crashes".

Indeed the same problem, this is a very strange. If all symbols cannot be found for an executable, normally it should not be possible to start it.

I think, you should try compiling from source.

George wrote:Indeed the same problem, this is a very strange. If all symbols cannot be found for an executable, normally it should not be possible to start it.

This is not right. Try to create a folder with following files:

test.c:

Code: Select all

void test() { }
void test2() { }


test.h:

Code: Select all

void test();
void test2();


main.c

Code: Select all

#include <stdio.h>
#include "test.h"

int main()
{
        test();
        printf("test\n");
        test2();
        printf("test2\n");
        return 0;
}


Now compile the shared library with "gcc -shared test.c -o libtest.so" and the main program with "gcc -Wl,-rpath=. main.c -o main -L. -ltest". The program should run fine with "./main". Now change test.h:

Code: Select all

void test();
/* void test2(); */


And recompile the the library with "gcc -shared test.c -o libtest.so". When you start the program you will notice that it stops after "test".

This can be changed by compiling the stuff with "gcc -Wl,-z,now -Wl,-rpath=. main.c -o main -L. -ltest". Please contact "man ld"

any solution

Moshroum wrote:

George wrote:Indeed the same problem, this is a very strange. If all symbols cannot be found for an executable, normally it should not be possible to start it.

This is not right. Try to create a folder with following files:

test.c:

Code: Select all

void test() { }
void test2() { }


test.h:

Code: Select all

void test();
void test2();


main.c

Code: Select all

#include <stdio.h>
#include "test.h"

int main()
{
        test();
        printf("test\n");
        test2();
        printf("test2\n");
        return 0;
}


Now compile the shared library with "gcc -shared test.c -o libtest.so" and the main program with "gcc -Wl,-rpath=. main.c -o main -L. -ltest". The program should run fine with "./main". Now change test.h:

Code: Select all

void test();
/* void test2(); */


And recompile the the library with "gcc -shared test.c -o libtest.so". When you start the program you will notice that it stops after "test".

This can be changed by compiling the stuff with "gcc -Wl,-z,now -Wl,-rpath=. main.c -o main -L. -ltest". Please contact "man ld"

Interesting I didn't know that, better add these linker flags then.

in kubuntu (installed from ubuntu amd64 package) crashes too

I have added the linker flags.

Can you please try the official KTorrent 2.0.2 packages, available at http://packages.ubuntu.com/dapper-backp ... t/ktorrent

Scroll down to the bottom and find the amd64 link.