Bug 701064 - [abrt] ktorrent-4.1.0-1.fc14: findNode: Process /usr/bin/ktorrent was killed by signal 11 (SIGSEGV)
Summary: [abrt] ktorrent-4.1.0-1.fc14: findNode: Process /usr/bin/ktorrent was killed ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: ktorrent
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Roland Wolters
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ac3ce46c507f9d128eda018addd...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-30 19:22 UTC by Mark Lambert
Modified: 2011-05-13 23:01 UTC (History)
5 users (show)

Fixed In Version: ktorrent-4.1.1-1.fc14
Clone Of:
Environment:
Last Closed: 2011-05-05 05:08:43 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (39.78 KB, text/plain)
2011-04-30 19:22 UTC, Mark Lambert
no flags Details


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

Description Mark Lambert 2011-04-30 19:22:45 UTC
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 40739 bytes
cmdline: ktorrent --nocrashhandler
comment: Simply open the program and let it run - this is the first time having run with the --nocrashhandler command line option.  Seemingly no difference with the option except that this time Abrt actually caught it.  Normally the program quietly crashes - on occasion the KDE Crash Handler has popped up and a backtrace was sent then as well.
component: ktorrent
Attached file: coredump, 164581376 bytes
crash_function: findNode
executable: /usr/bin/ktorrent
kernel: 2.6.35.12-90.fc14.i686
package: ktorrent-4.1.0-1.fc14
rating: 4
reason: Process /usr/bin/ktorrent was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1304190466
uid: 500

How to reproduce
-----
1.  No specific steps to reproduce - crashes are random and may occur after minutes, hours and occassionally a day or more between crashes.

Comment 1 Mark Lambert 2011-04-30 19:22:48 UTC
Created attachment 495993 [details]
File: backtrace

Comment 2 Fedora Update System 2011-05-02 11:47:04 UTC
ktorrent-4.1.1-1.fc15,libktorrent-1.1.1-1.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/ktorrent-4.1.1-1.fc15,libktorrent-1.1.1-1.fc15

Comment 3 Fedora Update System 2011-05-02 11:47:59 UTC
ktorrent-4.1.1-1.fc14,libktorrent-1.1.1-1.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/ktorrent-4.1.1-1.fc14,libktorrent-1.1.1-1.fc14

Comment 4 Fedora Update System 2011-05-02 22:26:09 UTC
Package ktorrent-4.1.1-1.fc14, libktorrent-1.1.1-1.fc14:
* should fix your issue,
* was pushed to the Fedora 14 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing ktorrent-4.1.1-1.fc14 libktorrent-1.1.1-1.fc14'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/ktorrent-4.1.1-1.fc14,libktorrent-1.1.1-1.fc14
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2011-05-05 05:08:34 UTC
ktorrent-4.1.1-1.fc15, libktorrent-1.1.1-1.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 6 Fedora Update System 2011-05-13 23:00:53 UTC
ktorrent-4.1.1-1.fc14, libktorrent-1.1.1-1.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.