Bug 669978 - [abrt] gpodder-2.8-2.fc14: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Summary: [abrt] gpodder-2.8-2.fc14: Process /usr/bin/python was killed by signal 11 (S...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gpodder
Version: 14
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Jef Spaleta
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:be6558a28055977a643fb4812ef...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-16 13:19 UTC by Steve Smethurst
Modified: 2011-01-16 22:36 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-01-16 22:36:10 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (60.96 KB, text/plain)
2011-01-16 13:19 UTC, Steve Smethurst 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Steve Smethurst 2011-01-16 13:19:37 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/gpodder
comment: I'm not sure I could reproduce it.  This is normal activity for me, and this is the first time GPodder has responded by crashing.
component: gpodder
executable: /usr/bin/python
kernel: 2.6.35.10-74.fc14.i686
package: gpodder-2.8-2.fc14
rating: 4
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1295183162
uid: 1000

How to reproduce
-----
1. GPodder had been working for a few days unattended
2. I was reading pages in Firefox, plugged in my usb podplayer, nautilus windows opened 
3. Gpodder crashed
Comment 1 Steve Smethurst 2011-01-16 13:19:41 UTC 
Created attachment 473698 [details]
File: backtrace
Comment 2 Ville-Pekka Vainio 2011-01-16 22:36:10 UTC 
The backtrace is incomplete and doesn't show where the crash is happening. The rest of the backtrace of thread one points to ffmpeg, which is not in Fedora. For these reasons, I'll close this bug. If you find out a way to reproduce the bug and get a complete backtrace, you can report the bug to the repository you installed ffmpeg from.
Note You need to log in before you can comment on or make changes to this bug.