Bug 382001 - KTorrent crashes on exit
Summary: KTorrent crashes on exit
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: ktorrent
Version: 8
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
Assignee: Roland Wolters
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-11-14 09:47 UTC by Michal Klich
Modified: 2007-11-30 22:12 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2007-11-16 23:36:10 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
log (6.15 KB, application/octet-stream)
2007-11-14 09:47 UTC, Michal Klich 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 152320 0 None None None Never

Description Michal Klich 2007-11-14 09:47:22 UTC 
Description of problem:
KTorrent crashes on exit.

Version-Release number of selected component (if applicable):
KTorrent 2.2.2

How reproducible:
It crashes randomly on exit.
Comment 1 Michal Klich 2007-11-14 09:47:22 UTC 
Created attachment 257851 [details]
log
Comment 2 Rex Dieter 2007-11-14 12:38:58 UTC 
You'll get better results (and ktorrent dev attention), if you take this
upstream to bugs.kde.org (or ktorrent's user forum), per recommendation of
http://ktorrent.pwsp.net/index.php?page=faq

When/if you do that, please let us know, so that we can continue to track the issue.
Comment 3 Michal Klich 2007-11-14 21:00:34 UTC 
I guess this ticket can be closed as i opened a ticket with bugs.kde.org. I got
bug number 152320.
Comment 4 Roland Wolters 2007-11-16 10:20:07 UTC 
Please test the newest version 2.2.3. According to the ktorrent developers 
that version should have fixed the crashes:
http://koji.fedoraproject.org/koji/buildinfo?buildID=24519
Comment 5 Michal Klich 2007-11-16 22:29:11 UTC 
Installed version 2.2.3 and testing it right now. If any troubles i will update
this log.
Comment 6 Roland Wolters 2007-11-16 23:36:10 UTC 
Bug closed for now, re-open when the same problem appears, open *another* one 
when other problems come up.
Note You need to log in before you can comment on or make changes to this bug.