Bug 618127 – [abrt] crash in qbittorrent-1:2.2.8-2.fc13: Process /usr/bin/qbittorrent was killed by signal 4 (SIGILL)

Bug 618127 - [abrt] crash in qbittorrent-1:2.2.8-2.fc13: Process /usr/bin/qbittorrent was killed by signal 4 (SIGILL)

Summary:	[abrt] crash in qbittorrent-1:2.2.8-2.fc13: Process /usr/bin/qbittorrent was ...

Status:	CLOSED DUPLICATE of bug 581760

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	qbittorrent (Show other bugs)
Sub Component:
Version:	13
Hardware:	i686 Linux

Priority	low Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	leigh scott
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:	abrt_hash:557ddd1c62e768e2a88d6d9d671...
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2010-07-26 04:18 EDT by John de Loos
Modified:	2010-07-29 08:21 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2010-07-29 08:21:38 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
File: backtrace (14.78 KB, text/plain) 2010-07-26 04:18 EDT, John de Loos	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description John de Loos 2010-07-26 04:18:52 EDT

abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: qbittorrent
component: qbittorrent
executable: /usr/bin/qbittorrent
global_uuid: 557ddd1c62e768e2a88d6d9d671171278a6d6423
kernel: 2.6.33.6-147.fc13.i686
package: qbittorrent-1:2.2.8-2.fc13
rating: 3
reason: Process /usr/bin/qbittorrent was killed by signal 4 (SIGILL)
release: Fedora release 13 (Goddard)

Comment 1 John de Loos 2010-07-26 04:18:55 EDT

Created attachment 434363 [details]
File: backtrace

Comment 2 leigh scott 2010-07-29 08:21:38 EDT


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

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