Two new releases on one day, first a new bugfix release in the 4.0 branch. It fixes several crashes, and other small issues in the µTP code. This will probably be the final release in the 4.0 series.

Next to this release the first beta of 4.1 has also been released. This is a testing release so that the new features in 4.1 can have their first test. The most notable changes in this release are:

* Video streaming support
* Superseeding support
* Data file moves are now tracked in the GUI
* The GUI has been redesigned and now makes proper use of KDE's KParts technologie
* The search plugin now uses webkit
* Exclusion patterns have been added to the syndication plugin filters

And many other smaller changes. For a full overview of all the changes, take a look in the ChangeLog's of libktorrent and ktorrent.

Sorry to tell you that 4.0.5 is still buggy on an [almost] fresh kubuntu 10.10 . If I'm not wrong, ktorrent is the only program I've compiled, so versions of Qt, KDE etc. are default 4.7.0 and 4.5.1 respectivly. It still crashes for no apparent reason after 15 minutes (more or less).

I don't know very well if it is worth to install the debugging programs for ktorrent from apt-get since it was compiled, so I don't know how could I help to detect the bug.

Please let me know if there's anything I could do.

Regards,

Nicolás

PD: I also tried to test 4.1 but I didn't have all dependencies. It seems it needs a newer QT or sth else.

Did you also install libktorrent 1.0.5 ?

Also it would be interesting to run ktorrent under valgrind, that usually leads to useful information.

Of course. I compiled first libktorrent 4.0.5 and then ktorrent 4.0.5.
98% of probabilities it is due to kubuntu... on Arch I haven't seen any crash, with any version, even with a ~/.kde4/share/apps/kde mapped to the kubuntu's one.

I'll take a look at valgrind. New music for me

Thank you George for the quick reply.

Regards,

Nicolás

Hi! here's a pastebin with valgrind output: http://pastebin.com/h5uFzdP6
Valgrind is still running although ktorrent already crashed at some point.

Please let me know what you read/conclude.

Thanks

Could you install Qt debug packages ?

It looks like this Qt bug:

http://bugreports.qt.nokia.com/browse/QTBUG-13963

But without debug information it is hard to be sure.

Ok, I see. Is there anything else I could do to help debugging?

if helps, here's another valgrind output: http://pastebin.com/MuALDKqe

Regards,

Nicolás

George wrote: * The GUI has been redesigned and now makes proper use of KDE's KParts technologie

i could not compile it, so show me screenshots please

I think I've got it:

nico@linksys:~$ ktorrent
QMetaObject::invokeMethod: No such method kt::App::loadCommandLineOptionsForNewInstance()
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
Warning: QFileSystemWatcher: failed to add paths: /home/nico/.config/ibus/bus
Warning: Bus::open: Can not get ibus-daemon's address.
nico@linksys:~$ Warning: QFile::remove: Empty or null file name #It showed the command prompt again, but went on.
KCrash: Application 'ktorrent' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
sock_file=/home/nico/.kde/socket-linksys/kdeinit4__0
Warning: QSocketNotifier: Invalid socket 16 and type 'Read', disabling...
Unable to start Dr. Konqi

Is all the crash because of QFile::remove ?? I just did a sudo chown nico -R .kde/
Let's see what happens!

To Wishlist: check ownership of home folder and notice the [ignorant] user.

Regards

Post the backtrace

Which trace? Valgrind or KRash Handling events? I'm now installing qt debugging symbols. And I'll run Ktorrent again under valgrind. New posts comming

Here's my bug-report with Qt Debugging Symbols.

https://bugs.kde.org/show_bug.cgi?id=262933

Regards,

Nicolás

PD: The person in charge (Joris Guisson) says it's already fixed in the 1.1 branch (?), guess he refered to 4.1 and libkt. 1.1
I'll take a look; but a list of dependencies to compile 4.1 will be appreciated. EDIT: the ones in the wiki/FAQ are alright, but there's one surely missing: libgcrypted. Couldn't find any edit button on the wiki; or firefox doesn't remember my password ... lol Please someone add that dependency.

Hi! I've been using v4.1beta1 for a week now. It's far more stable than 4.0.5, but still not bulletproof It still hangs for no apparent reason after some hours; but the Qt debbugging symbols are not started after the crash. For 4.0.5, Dr. Konqui was launched just after a crash. Am I missing something? Does v4.1b1 need another debbugging different from 4.0.5 ?

Thanks

nicoadamo wrote:Hi! I've been using v4.1beta1 for a week now. It's far more stable than 4.0.5, but still not bulletproof It still hangs for no apparent reason after some hours; but the Qt debbugging symbols are not started after the crash. For 4.0.5, Dr. Konqui was launched just after a crash. Am I missing something? Does v4.1b1 need another debbugging different from 4.0.5 ?

Thanks

Have you compiled with debug information ?