By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 461 - KTorrent crashes almost immediately
Summary: KTorrent crashes almost immediately
Status: RESOLVED DUPLICATE of bug 443
Alias: None
Product: TDE
Classification: Unclassified
Component: non-core programs (show other bugs)
Version: 3.5.13 [Trinity]
Hardware: amd64 Debian Squeeze
: P5 normal
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2011-03-17 11:14 CDT by EJ Carscallen
Modified: 2012-10-19 15:47 CDT (History)
3 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description EJ Carscallen 2011-03-17 11:14:42 CDT 
Hello!  Thanks so much for the Trinity Desktop because I love KDE3 to an almost unnatural extent. All that aside, I had some trouble with a Trinity package. I installed KTorrent-Trinity (4:3.5.12-0 DEBIAN7+R1106865) through the package manager. I immediately added a torrent, but within seconds KTorrent crashes and shows in the Terminal:

"Error traversing database for IP num = [somenumbers] - Perhaps database is corrupt"

From googling this line it seems this is an error with "GeoIP" lookups?  I tried deleting the GeoIP.dat file in the hopes it would regenerate it's database correctly but this had no effect. Even though it crashes in seconds, the file had actually downloaded properly (it was very small) after several restart attempts and running KTorrent in debug mode shows connections established and everything appears fine until the GeoIP lookup.  Any thoughts on fixing or working around this issue would be greatly appreciated! Thanks so much for keeping my favorite DE alive!!
Comment 1 Slávek Banko 2012-03-01 09:26:22 CST 
This error caused by plugin Info Widget.

*** This bug has been marked as a duplicate of bug 443 ***